If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.



From BoxMatrix

BoxMatrix >> System >> TME @ BoxMatrix   -   IRC-Chat   -   Translate: de es fr it nl pl
News Selectors Models Accessories Components Environment Config Commands System Webif Software Develop Lexicon Community Project Media

Devices Filesystems Partitions Sockets Netlink Pipes Interfaces Bridges Ports Events Sources Sinks AVMIPC Processes Watchdogs Memory Slab Vmalloc ProcFS SysFS Research


Goto:   Dependencies   -   Model-Matrix   -   Missing Supportdata   -   SMW-Browser


TME is the Qualcomm Trusted Management Engine partition. It contains the first instance of the OS running on the TME.
The label of this partition is originally named 0:TME, which is an invalid article name in Mediawiki.

Qualcomm names a TME as a security feature of their Snapdragon 7 / 8 mobile platforms.
There it is part of the Secure Processing Unit (SPU). As usual there are no public manuals for it.

There's a PDF manual of the Qualcomm SPU260 Security Target Lite used in another Qualcomm SoC.
Chapter explains the hardware and functions of the TME subsystem. Excerpt from its introduction:

The TME subsystem is a separated part of the TOE but within the SoC and in charge of
the early stages of the secure boot process. It is composed by the TME CPU which runs
the TME PBL, TME Core Firmware and TME Core Software in its own RAM and the
TME Sequencer, which runs the TME Sequencer Firmware and TME Sequencer
Software. The TME Sequencer drives the steps during the secure boot while the TME
CPU is finally in charge of bringing the SPU out of reset in this process. Only these
modules related to secure boot are considered involved in the security functionality as

[ TOE = Target of Evaluation = SPU + TME ]
[ SFR = Security Functional Requirement ]

So far there's no evidence of a TME inside the Miami besides the TME / TME_1 partition names.

For cryptography the Miami uses the proprietary qca-nss-eip.ko / qca-nss-eip-crypto.ko EIP197 driver modules.
Maybe the TME also runs the EIP197 hardware crypto accelerator backend.

Multi-EVA boot on Qualcomm ARM: (Hawkeye, Alder, Miami, Dakota, Maple)


Daily updated index of all dependencies of this partition. Last update: GMT.
A * in the Mod column marks info from Supportdata-Probes, which will always stay incomplete.
A ** in the Mod column marks info from Supportdata2 probes, which by their nature will stay way more incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the item occurs, not the Relation.

Relation Typ Object Mod Firmware Info Origin
0 dependencies for this partition


Daily updated index of the presence, path and size of this partition for each model. Last update: 2024-07-17 06:19 GMT.
Showing all models using this partition. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom) label in the Model column shows which CPU is meant for models with multiple Linux instances.
Note that this list comes from Supportdata-Probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata file or just a disabled feature.

Missing Supportdata

The data in this article is incomplete due to missing Supportdata-Probes for the models listed below.
If you own any of these models and would like to help then please get in touch.


Information is currently being retrieved from the backend.


Showing 1 related property.