Visible to Intel only — GUID: GUID-DBBC3697-B05C-41A4-9E6D-52FE8CB96F4F
For API Level 1 - Intel® ME 7.x - Sandy Bridge
For API Level 1.1 - Intel® ME 8.x lite - Sandy Bridge
For API Level 2 - Intel® ME 8.0 - Ivy Bridge
For API Level 3 - Intel® ME 8.1 - Ivy Bridge
For API Level 3 - SEC1.0, SEC1.1, SEC1.2, SEC2.0
For API Level 4 - Intel® ME 9.5, Intel ME 9.5.55 - Haswell
For API Level 4 - Intel® ME 9.1, Intel ME 9.1.35 - Haswell
For API Level 5 - Intel® ME 10.0.0 - Haswell
For API Level 6 - Intel® ME 10.0.20 - Broadwell
For API Level 7 - ME 11.0 - Skylake_LP and Skylake_H
For API Level 8 - TXE3.0 - Broxton, ME 11.5/11.8 - Kabylake_LP, Kabylake_H
For API Level 9 - Intel® ME 12.0 - Cannon Lake
Trusted Application Validation Guidelines
Validating the Manifest
Memory and Performance
Error Handling and Recovery
Functional Validation and Multi-Instance Support
Pack and DALP Generation and Validation
Host-Side Software Validation Guidelines
Trusted Application Management Flows
Error Handling and Recovery Flows
Multi-Instance and Interoperability Testing of Trusted Application Management
General and Platform-Related Events
End-to-End and Setup Validation Guidelines
Cross Trusted Application Interoperability Functional Testing
Creating a New Project
Importing an Existing Project
Converting an Existing Project
Building and Packaging Your Project and Running in Emulated Environment
Running Your Project
Running and Testing on Emulation and on Silicon
Debugging Trusted Applications
Preparing and Submitting Your Project for Signing
Signing an Applet
Signing New Versions
Visible to Intel only — GUID: GUID-DBBC3697-B05C-41A4-9E6D-52FE8CB96F4F
Heap Memory
Memory allocated for and by the trusted application at run time is also allocated from a pool of total heap memory for all trusted applications. Here too, decreasing the memory needed to be allocated will increase the possibility of running more trusted applications. It should be noted that this memory includes memory explicitly allocated by the trusted application as well as memory allocated by the System for use with the trusted application, such as stack memory, meta data and other memory needed by the System to support running the trusted application.
Trusted applications should not require a heap larger than 64K bytes. If the trusted application uses the UI interface then it may need a heap as large as 90K bytes. Decreasing the trusted application code memory footprint will increase the possibility of loading the trusted application when there are other trusted applications already loaded; further, a smaller trusted application will leave more room for other trusted applications.
The SDK in Intel® DAL provides memory profiling tools (built into the firmware emulators - see Determining Actual Memory Requirements for a Trusted Application) to measure the trusted application heap usage. Use the tools to run the entire end-to-end flow of the trusted application (causing the maximum memory usage) to determine the heap usage. Because of the potential of heap fragmentation, it is recommended to add 40% to the estimated trusted application heap usage and use that value as a manifest parameter. You can reduce the impact of fragmentation by allocating larger needed chunks of memory first. Let the garbage collector handle the memory that you are not using. Do not save anything you do not need to hang on to.
Tip: In the Host - Trusted Application Communication flow, the buffer allocation for both Send and Receive operations is taken from the heap of the Trusted Application. In order to minimize the heap size needed, it is recommended not to use buffer sizes that are larger than a few kilobytes.