Page 1 of 9
#1 Intel Trusted Execution Engine: Drivers, Firmware & System Tools by plutomaniac 24.11.2014 17:58

avatar

Intel Trusted Execution Engine:
Drivers, Firmware & System Tools


Last Updated: 2017-12-12

Intel Trusted Execution Engine Introduction: Built into many Intel Chipset-based platforms is a small, low power computer subsystem called the Intel Trusted Execution Engine (Intel TXE). This can perform various tasks while the system is booting, running or sleeping. It operates independently from the main CPU, BIOS & OS but can interact with them if needed. The TXE is responsible for many parts of an Intel-based system. Such functionality extends, but it's not limited, to Platform Clocks Control (ICC), Thermal Monitoring, Fan Control, Power Management, Overclocking, Silicon Workaround (resolves silicon bugs which would have otherwise required a new cpu stepping), Identity Protection Technology, Boot Guard, Rapid Start Technology, Sensor Hub Controller (ISHC), Wireless Display, PlayReady, Protected Video/Audio Path etc. Thus it is essential for it to be operational in order for the platform to be working properly.

Intel Converged Security Engine Introduction: The evolution of Intel Trusted Execution Engine into a unified security co-processor, running x86 code under a Minix-based Operating System. It was first introduced in 2016 with the release of Apollo Lake CPUs working alongside Broxton SoC. The CSE hardware can run Management Engine (ME) 11+, Trusted Execution Engine (TXE) 3+ or Server Platform Services (SPS) 4+ firmware. So there are a total of three families of CSE-based firmware: CSME (CSE ME), CSTXE (CSE TXE) and CSSPS (CSE SPS).

This is a collection of everything Intel (CS)TXE related. To extract most of the files below you need to use programs which support RAR5 compression!

Disclaimer: All the software & firmware below comes only from official updates which were provided and made public by various manufacturers! The System Tools are gathered and provided with the sole purpose of helping people who are out of other viable solutions. Thus, they can be extremely helpful to those who have major problems with their systems for which their manufacturer refuses to assist due to indifference and/or system age.

A. About Intel TXEI Drivers

TXEI v4 drivers are usable with Gemini Lake systems. TXEI v3 drivers are usable with Apollo Lake systems. TXEI v2 drivers are usable with Bay Trail and Cherry Trail/Braswell systems. In order to check your current installed version, use ME Analyzer or TXEInfo tool as instructed below.

Note: To extract some of the files below you need to use programs which support RAR5 compression!

Note: TXEI v4 driver versions start with the year & week of release (example: 1731 --> 31st week of 2017).

A1. Intel TXEI Driver Only

These packages contain only the Intel TXEI driver without any additional software or system services. They are compatible with all TXE firmware SKUs.


A2. Intel TXEI Drivers & Software

For those looking for extra functionality, these are the full Drivers & Software. These packages contain the Intel TXEI drivers with their respective software & system services. All TXE firmware SKUs use the same drivers & software.


Note: TXEI Driver & Software v1731.4.0.1199 package includes v1731.4.0.1199 TXEI driver. TXEI Driver & Software v3.1.50.2222 package includes v3.0.0.1115 TXEI driver. TXEI Driver & Software v2.0.2.2092 package includes v2.0.0.1094 TXEI driver.

B. About Intel TXE v1 & v2 Firmware Updates

General Notice: Be careful of what firmware your download relevant to your system. First, make sure that you know what series it is (examples: Apollo Lake, Cherry Trail, Braswell, Bay Trail). Then run TXEInfo Tool and check the "FW Version" line to determine your TXE firmware version (examples: 2.0.0.2060 --> v2.0, 1.1.2.1120 --> v1.1). All the firmware below correspond to a specific series which comes with a specific TXE firmware version (example: For Bay Trail systems which come with TXE v1.1).

Security Version Number (SVN): All (CS)TXE firmware are defined by a Security Version Number (SVN) like 1,2,3 etc which is used to control the possible upgrade/downgrade paths provided by Intel's FWUpdate tool. The SVN gets incremented if there is a high or critical security fix that requires a Trusted Computing Base (TCB) recovery operation, a significant event in the life cycle of the firmware which requires renewal of the security signing keys in use. A downgrade to a lower SVN value via FWUpdate tool is prohibited whereas an upgrade to the same or higher SVN is allowed. For example if your current firmware has a SVN of 2, you can update to another firmware with SVN >= 2 (for example 3) but you cannot downgrade to another firmware with SVN < 2 (for example 1). Trying to flash a firmware with lower SVN will result in the error "The image provided is not supported by the platform" or similar. This upgrade/downgrade control method applies to Intel's FWUpdate tool only and not when using a hardware SPI programmer or any general SPI software flasher such as Intel's Flash Programming Tool, Flashrom, AFU etc. To view the SVN value of any TXE firmware, you can use ME Analyzer tool.

Version Control Number (VCN): All (CS)TXE firmware are defined by a Version Control Number (VCN) like 1,2,45,193 etc which is used to control the possible upgrade/downgrade paths provided by Intel's FWUpdate tool. The VCN gets incremented if there is a security fix, a significant firmware change or a new feature addition. A downgrade to a lower VCN value via FWUpdate tool is prohibited whereas an upgrade to the same or higher VCN is allowed. For example if your current firmware has a VCN of 176, you can update to another firmware with VCN >= 176 (for example 193) but you cannot downgrade to another firmware with VCN < 176 (for example 174). Trying to flash a firmware with lower VCN will result in the error "The image provided is not supported by the platform" or similar. This upgrade/downgrade control method applies to Intel's FWUpdate tool only and not when using a hardware SPI programmer or any general SPI software flasher such as Intel's Flash Programming Tool, Flashrom, AFU etc. To view the VCN value of any TXE firmware, you can use ME Analyzer tool.

Firmware Regions (RGN/EXTR): The SPI/BIOS chip firmware is divided into regions which control different aspects of an Intel-based system. The mandatory regions are the Flash Descriptor (FD, controls read/write access between the regions among other things), the Engine (TXE, holds the TXE firmware which has been configured for a specific system) and the BIOS. The TXE firmware is neither static nor identical across different systems. Its code at the Engine region is always Configured by the manufacturer (OEM) as explained at Section A of the CleanUp Guide. The Type of each TXE firmware can be either Stock Region (RGN, clean/stock/unconfigured images provided by Intel to OEMs) or Extracted Region (EXTR, dirty/extracted/configured images from various SPI/BIOS). The TXE firmware at the system's SPI/BIOS chip is always EXTR, generated by the OEM after configuring the equivalent RGN. Never flash RGN firmware to the Engine region without first configuring them for your specific system (EXTR) via Intel's Flash Image Tool. The use of any software (Intel's Flash Programming Tool, AMI's AFU, Flashrom etc) or hardware (programmer) firmware flasher, which directly deals with the Engine region of the SPI/BIOS chip, requires prior configuration of TXE RGN to EXTR firmware.

Firmware Updates (UPD): To allow quick and effortless on-field updating of the TXE firmware, Intel provides a tool called FWUpdate. Update images (UPD) are partial Firmware Regions which contain only TXE "CODE" without any "DATA" (read Section A of the CleanUp Guide). They are created and used only by Intel's FWUpdate tool. Thus, they can neither be opened nor configured by Intel's Flash Image Tool. Never flash UPD firmware to the Engine region via anything other than FWUpdate tool. UPD images exist but are not needed for TXE systems as FWUpdate can update the TXE firmware with all three possible Types (RGN/EXTR/UPD). Thus, at all Bx sections below, only RGN/EXTR images are provided.

SKUs: TXE Firmware v1.0 is divided into two SKUs: Thin 1.25MB and Full 3MB. TXE Firmware v1.1 and v1.2 have combined the two previous SKUs into a single 1.375MB SKU. TXE Firmware v2.0 has a single 1.375MB SKU. To determine your SKU, ME Analyzer (by loading your BIOS file) or TXEInfo can help you sort most system specific details.

TXE 1.x Upgradeability: Intel TXE v1.0 firmware (Full 3MB & Thin 1.25MB) can be upgraded to v1.1 or v1.2 firmware (1.375MB). However, the upgrade process can not be done using FWUpdate tool. Instead, FPT (Flash Programming Tool) must be used with a configured (by Flash Image Tool) TXE region while in manufacturing mode (unlocked Flash Descriptor).

B1. TXE v2.1 Firmware-based Systems


B2. TXE v2.0 Firmware-based Systems


B3. TXE v1.2 Firmware-based Systems


B4. TXE v1.1 Firmware-based Systems


B5. TXE v1.0 Firmware-based Systems


C. About Intel (CS)TXE System Tools

The Intel (CS)TXE System Tools are used for creating, modifying, and writing binary image files, manufacturing testing, Intel (CS)TXE setting information gathering and Intel (CS)TXE firmware configuration and updating. These tools are not released to end-users but only to OEMs. The software below comes only from official updates which were provided and made public by various OEMs.

Flash Image Tool: Creates and configures a complete SPI image file which includes regions Flash Descriptor Region, BIOS, Intel integrated LAN (GbE), Intel (CS)TXE & Platform Descriptor Region. The user can manipulate the completed SPI image via a GUI and change the various chipset parameters to match the target hardware.

Flash Programming Tool: Used to program a complete SPI image into the SPI flash device(s). FPT can program each region individually or it can program all of the regions with a single command. The user can also use FPT to perform various functions such as view the contents of the flash on the screen, write the contents of the flash to a log file, perform a binary file to flash comparison, write to a specific address block, program fixed offset variables etc.

C1. Identifying, Diagnosing & Updating Intel (CS)TXE Firmware

Those who are looking to update/downgrade their firmware should use TXEInfo, FWUpdate & TXEManuf tools for status information, updating and functionality checking accordingly. The information & instructions below apply to these three tools only and can be found inside the full Intel TXE System Tools Packages.

TXEInfo: Checks that the (CS)TXE is operating normally on the software/firmware level by querying the (CS)TXE device on its status. Make sure it doesn't report any red errors. The yellow "GBE Region does not exist" warning is normal for systems that don't have an Intel GbE Controller, you can safely ignore it.

TXEManuf: A diagnostic tool which can be used to run certain manufacturing-line tests to ensure that the (CS)TXE is working properly on the hardware level. It should report a green message such as "TXEManuf Operation Passed".

FWUpdate: Used to upgrade or downgrade the (CS)TXE firmware. FWUpdate can work with all firmware Types (RGN/EXTR/UPD) and does not change any (CS)TXE configuration settings (DATA section) which are model or system specific.

C2. Intel (CS)TXE System Tools

Note: To extract the files below you need to use programs which support RAR5 compression!

#2 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by plutomaniac 13.12.2014 00:57

avatar

Updates since 24/11/2014:

NEW! TXE v1.1 (1.375MB) Firmware from v1.1.0.1115 (VCN ~8) --> v1.1.2.1120 (VCN 11)
NEW! TXEI Drivers & Software from v1.1.0.1113 --> v1.1.2.1120 complete installer package

* Updated TXEI Drivers v1.1.0.1064 (same driver from 01/2014, new security catalog from 09/2014)
* Added at TXE System Tools v1.1: Intel TXE FW v1.1.2.1120 HF Release Communication documentation
* Updated at TXE System Tools v1.1: Bay Trail TXE Firmware Release Notes v1.1.0.1089 --> v1.1.2.1120 documentation
* Updated at TXE System Tools v1.1: Bay Trail TXE FW Bring Up Guide v1.7 (02/2014) --> v1.7 (09/2014) documentation
* Updated at TXE System Tools v1.1: System Tools User Guide v1.3 (10/2013) --> v1.4 (04/2014) documentation
* Updated at TXE System Tools v1.1: Flash Image Tool from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: Flash Manifest Generation Tool from v1.1.0.1089 --> v1.1.2.1120
* Updated at TXE System Tools v1.1: Flash Programming Tool(Android) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: Flash Programming Tool(EFI) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: Flash Programming Tool(EFI32) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: Flash Programming Tool(Windows) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: Flash Programming Tool(Windows64) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: FWUpdate(Android) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: FWUpdate(LocalEfi32) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: FWUpdate(LocalEfi64) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: FWUpdate(LocalWin32) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: FWUpdate(LocalWin64) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: TXEInfo(Android) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: TXEInfo(EFI) from v1.1.0.1113 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: TXEInfo(EFI32) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: TXEInfo(Windows) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: TXEInfo(Windows64) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: TXEManuf(Android) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: TXEManuf(EFI) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: TXEManuf(EFI32) from v1.1.0.1113 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: TXEManuf(Windows) from v1.1.0.1089 --> v1.1.1.1120
* Updated at TXE System Tools v1.1: TXEManuf(Windows64) from v1.1.0.1089 --> v1.1.1.1120

Note: I know the latest v1.0 firmware is v1.0.5.1120. If you can find it by aqcuiring a full package, extracting it from a BIOS, using FWUpdate -save etc please share it here.

#3 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by Pacman 19.01.2015 21:04

avatar

Hello :)

TXE 3MB firmware 1.0.5.1120 i have not tested as i don't have the suitable HW.

#4 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by plutomaniac 19.01.2015 21:45

avatar

Pacman, thank you very much for being the first to contribute in TXE and for keeping an eye out for such firmware & drivers. It seems that it was extracted from a BIOS. Can you tell me which one? Such info can be useful in order to check if they have also uploaded the equivalent full package or if I can find the VCN number.

I cannot test these as well because I don't have the hardware. If anyone has used the firmware, tools & drivers successfully please let us know here.

#5 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by Pacman 19.01.2015 22:07

avatar

Yes, it was extracted from this Intel NUC BIOS:
https://downloadcenter.intel.com/Detail_...g&DwnldID=24512

#6 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by plutomaniac 20.01.2015 12:33

avatar

NEW! Intel TXE1.0 Firmware 1.25MB from v1.0.4.1089 (VCN ~8) --> v1.0.5.1120 (VCN ~8)
NEW! Intel TXE1.0 Firmware 3MB from v1.0.4.1090 (VCN ~8) --> v1.0.5.1120 (VCN ~8)

#7 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by plutomaniac 23.01.2015 18:37

avatar

Update:

So, I figured out how to determine the VCN when a TXE firmware is extracted from UEFI images:

TXE 1.25MB: 13034h
TXE 3MB: 43034h
TXE 1.375MB: 67034h

The SVN number is most probably 4 bytes to the left meaning:

TXE 1.25MB: 13030h
TXE 3MB: 43030h
TXE 1.375MB: 67030h

TXE_Header_Info.PNG - Bild entfernt (keine Rechte)

Re-Upload! Intel TXE1.0 Firmware 1.25MB v1.0.5.1120 (VCN 11)
Re-Upload! Intel TXE1.0 Firmware 3MB v1.0.5.1120 (VCN 11)

#8 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by lordkag 23.01.2015 21:55

avatar

I have found recently an Intel TXE Firmware 1.0.6.1120 in a HP BIOS, didn't noted which one. Most likely a 3MB one.

Also attached other older versions I have. Ignore the names for now, I will see if I can add a TXE detection to my Extractor. With Igor's script and your help, it shouldn't be that hard. It seems you already gone further than Igor:

ME-Tools.png - Bild entfernt (keine Rechte)

#9 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by plutomaniac 24.01.2015 00:45

avatar

NEW! Intel TXE1.0 Firmware 3MB from v1.0.5.1120 (VCN 11) --> v1.0.6.1120 (VCN 11)

Lordkag, thank you for the newer FW. It's funny, I found that version some hours before your post at HP as well. But I couldn't extract the damn BIOS image at all. Have you written your own scripts to extract those after identifying the compression?

Anyway, this a 3MB SKU. Here are all the different HP packages with that version - maybe some other has the 1.25MB variant. Can you please extract those as well?

http://h20564.www2.hp.com/hpsc/swd/publi...b-142261-1#tab2
http://h20564.www2.hp.com/hpsc/swd/publi...b-142260-1#tab2
http://h20564.www2.hp.com/hpsc/swd/public/detail?swItemId=ob_141216_1&#tab2 --> (Extracted, 3MB)

Now, to fix your extractor properly here are some usefull info:

04 00 00 00 67 5C FF 0D 03 43 00 00 --> $SKU for 1.25MB (v1.0) & 1.375MB (v1.1)
04 00 00 00 67 5C FF 0D 05 43 00 00 --> $SKU for 3MB (v1.0)

That is: 135E0h for 1.25MB, 438E0h for 3MB & 67760h for 1.375MB SKUs respectively.

Once the $SKU is determined the size to extract is as follows (based on Intel bin size, anything larger is useless FF padding):

1.25MB (v1.0) --> 140000h
3MB (v1.0) --> 300000h
1.375MB (v1.1) --> 160000h

Also, I have uploaded a new "collection" of TXE firmware. I have added some of my own older firmware, corrected the names & sizes by adding or removing padding and correctly determined each firmware's SKU:

ALL_TXE_FW.PNG - Bild entfernt (keine Rechte)

EDIT: File updated with v1.0.0.1058_3MB & 1.0.4.1090_3MB firmware images.

#10 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by lordkag 24.01.2015 19:57

avatar

They are not compressed, but encrypted. One of the "features" HP is offering to customers is full lock-down on their paid products. What I do is extract that .exe until I get to this folder:

HP_unpack.png - Bild entfernt (keine Rechte)

Then I run InsydeFlash, which (after analysing the system) offers these options:

HP_select.png - Bild entfernt (keine Rechte)

where you choose the folder to unpack the unencrypted content. If for some reason the flasher disables the options (happens on newer versions), I use the attached older flasher and drop the file with .fd extension. Anyway, all of the above links have a 3M firmware, with sp69922.exe offering a clean firmware, which you might want to use instead of the one I uploaded.

I added TXE detection, by checking the size of modules (those starting with $MME). If it is 0x60, we have ME, if it is 0x80 (0x60 + 0x20 reserved), we have TXE. I also added TXE variant detection, by checking the start of first $MN2 section. If it is 0x13000 = 1.25M, 0x43000 = 3M, 0x67000 = 1.375M. If this fails, I will read the SKU and check the major.minor version: 67 5C FF 0D 03 43 and 1.0.x = 1.25MB, 67 5C FF 0D 03 43 and 1.1.x = 1.375MB, 67 5C FF 0D 05 43 = 3MB.

I don't know about the size. The extraction happens before, at regions display, by analysing the descriptor (thanks to CodeRush). Only if the region is smaller than 0x1FFFFF, I use 0x17D000 for 1.5MB. The detection happens later, at ME version display, so I don't feel like using the detection twice. Plus, if you look at 1.0.0.1055_1.25M, the last section should start at 0xAC000 and be 0x99000 in size, reaching 0x145000. Even though only padding is after 0x140000 limit, it still cuts the original structure, with possible complaints from the flasher. So, for now I leave this on hold.

#11 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by plutomaniac 25.01.2015 01:25

avatar

Thanks for explaining the encrypted HP binaries and for the files.

The difference between sp70119/sp70118 & sp69922 is whether NFC is enabled or disabled. If you enable/disable it at both the code will be identical (apart from 1,2 bytes at $FPT header -> useless). It seems that every time you Build a TXE image at FITC, a version will be added at $FPT header where it's usually FF at Production images. I said a version because the weird thing is that sometimes that version is wrong. For example at v1.0.5 & 1.0.6 images (extracted by FITC) it reports 1.0.4 at the $FPT header (of course it's correct at $MN2). I've seen this before regarding TXE. Maybe, 1.0.5 & 1.0.6 are based on 1.0.4 and this is kept somewhere for some reason. Or maybe it's a bug. I will reupload the "FF at $FPT" version (as I like to call it) here so that it's "clean". I don't know what's the deal with NFC being enabled & disabled, my guess is that FWUpdLcl won't care either way.

Zitat von lordkag im Beitrag #10
Plus, if you look at 1.0.0.1055_1.25M, the last section should start at 0xAC000 and be 0x99000 in size, reaching 0x145000.

I don't understand, how do you check the size exactly? At $SKU for example it makes sense to me (04 00 00 00 or 4 * 3 = 12 or 0xC). According to Igor, the size of $MN2 is between 18 & 1B. So, at the last $MN2 of 1.0.0.1055_1.25MB firmware that would be: FE 00 00 00 or 254 * 3 = 762 or 0x2FA. Where am I wrong?

You mentioned something about 1.0.0.1055_1.25MB and the it's size (regions getting cut-off even though it's just padding). Let me explain: I don't think 1.0.0.1055 is a credible TXE firmware. If you notice, all other (newer) 1.25MB firmware start the last $MN2 region at a different offset (0xA5000) and do not contain extra data after the $MN2 size (as calculated above) in contrast to 1.0.0.1055 (0xAC000). I remember back at November when I first wrote this thread that TXE started differently. Some old documentation (from the original 1.0.0.1050 package, can't find it anymore unfortunately) mentioned only one v1.0 firmware SKU and it wasn't 1.25MB or 3MB. TXE kept changing at the beginning so old firmware are not really credible. A perfect example of that is the fact that originally v1.1 firmware was supposed to be 3MB in size but with the first PV release (1.1.0.1089) that was changed to 1.375MB, a mixture between the Thin (1.25MB) and Major/Full (3MB) v1.0 SKUs. So for the exact same reason, 1.1.0.1073 is not a credible TXE firmware. Here:

TXE_1.1.0.1073_Alpha_3MB.PNG - Bild entfernt (keine Rechte)

I also know that the versions & dates are completely messed up. For example:

1.0.0.1050 (3MB) --> 20/08/2013
1.0.0.1055 (1.25MB) --> 16/07/2013
1.0.0.1058 (3MB) --> 06/08/2013
1.0.2.1060 (3MB) --> 20/08/2013

1.0.5.1120 (3MB) --> 17/08/2014
1.0.6.1120 (3MB) --> 11/08/2014

Adding to the (already too much) confusion, firmwares 1.0.0.1058 & 1.0.2.1060 seemed to coexist at some point for some reason. Even though the official 1.0.2.1060 has no mention of 1.0.0.1058 and the 1.0.0.1058 package does not mention 1.0.2.1060, at an early 1.0.2.1060 package we can see this:

0.1058_2.1060.PNG - Bild entfernt (keine Rechte)

On the other hand, all v1.1 dates make sense as far as I can see. Finally!

Generally: TXE has changed so much since the beginning (early 2013) and that makes it difficult to understand it sometimes. Especially with no users reporting on whether the above are even working. I was also wondering whether a special TXE is required for Bay Trail-T (Tablets) compared to Bay Trail-M/D (Mobile/Desktop). That's neither here nor there though so I guess I'll find out at some point.

Sources (Kits & Documentation) containing 1.0.0.1058, 1.0.2.1060 (early), 1.0.2.1060 (release) & 1.1.0.1073: http://www.mediafire.com/download/sx3qbq...&_1.1.0.1073.7z

Attached new TXE firmware "collection" including v1.1.0.1073.

#12 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by lordkag 26.01.2015 18:11

avatar

Offset of sections:

ME_offset.png - Bild entfernt (keine Rechte)

I also noticed the date between 1.0.5.1120 and 1.0.6.1120. But your 1.0.0.1050 (3MB) is actually 1.0.2.1060 (3MB)

ME_vers.png - Bild entfernt (keine Rechte)

#13 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by plutomaniac 07.05.2015 00:43

avatar

Say hello to TXE 2.0 Firmware, Tools & Drivers. These are for Braswell & Cherry Trail SoCs.

Updates:

NEW! Intel TXE 2.0 1.375MB Firmware v2.0.0.2060



NEW! Intel TXE System Tools v2.0 r1

Flash Image Tool: 2.0.0.2056
Flash Manifest Generation Tool: 2.0.0.1056
Flash Programming Tool(EFI): 2.0.0.2056
Flash Programming Tool(EFI32): 2.0.0.2056
Flash Programming Tool(Windows): 2.0.0.2056
Flash Programming Tool(Windows64): 2.0.0.2056
FWUpdate(LocalEfi32): 2.0.0.2056
FWUpdate(LocalEfi64): 2.0.0.2056
FWUpdate(LocalWin32): 2.0.0.2056
FWUpdate(LocalWin64): 2.0.0.2056
TXEInfo(EFI): 2.0.0.2056
TXEInfo(EFI32): 2.0.0.2056
TXEInfo(Windows): 2.0.0.2056
TXEInfo(Windows64): 2.0.0.2056
TXEManuf(EFI): 2.0.0.2056
TXEManuf(EFI32): 2.0.0.2056
TXEManuf(Windows): 2.0.0.2056
TXEManuf(Windows64): 2.0.0.2056

NEW! Intel TXEI Driver v2.0.0.1057 INF for manual installation
NEW! Intel TXEI Drivers & Software v2.0.0.2058 complete package
NEW! Intel TXEInfo Tool for TXE 2.0 Firmware v2.0.0.2056
NEW! Intel TXEManuf Tool for TXE 2.0 Firmware v2.0.0.2056
NEW! Intel FWUpdate Tool for TXE 2.0 Firmware v2.0.0.2056

#14 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by plutomaniac 05.06.2015 01:16

avatar

Updates 05/06/2015:

NEW! Intel TXE Firmware v1.1.1.1130 (1.375MB BYT-I)
NEW! Intel TXE Firmware v1.0.5.1120 (3MB BYT-MD)
NEW! Intel TXE Firmware v1.0.2.1067 (1.25MB BYT-I)
Reuploaded: Intel TXE Firmware v2.0.0.2060 (1.375MB) from EXTR --> RGN
Reuploaded: Intel TXE Firmware v1.1.2.1120 (1.375MB BYT-MD)
Reuploaded: Intel TXE Firmware v1.0.5.1120 (1.25MB BYT-MD)
Reuploaded: Intel TXE Firmware v1.0.6.1120 (3MB BYT-I)

Note: TXE 1.x firmware is different for Bay Trail Mobile/Desktop (BYT-M/D) and for Bay Trail Tablet/IVI (BYT-I). All variants are now uploaded but 1.25MB BYT-I is not at the latest version of 1.0.6.1120. When I found it, it will be replaced.

Since there is no way to distinguish the two variants apart (BYT-M/D and BYT-I) via a tool such as ME Analyzer: When you find a new firmware, try to mention from what SPI image (BIOS) it came as well or which system. Preferably, attach the whole SPI/BIOS image for me to investigate.

#15 RE: Intel Trusted Execution Engine: Drivers, Firmware & System Tools by plutomaniac 08.06.2015 20:30

avatar

Updates 08/06/2015:

Intel TXE System Tools v1.1 from r1 --> r2:

Updated Intel TXE FW Update Customer Communication from v1.1.0.1089 --> v1.1.0.1113

Intel TXE System Tools v1.0 from r1 --> r2:

Added Intel TXE FW Update Customer Communication v1.1.0.1113 (for page 12)

Xobor Forum Software von Xobor