Visible to Intel only — GUID: GUID-633BFB55-2A08-4320-83FB-FA65BED9D4BF
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-633BFB55-2A08-4320-83FB-FA65BED9D4BF
Manifest Fields Format Rules
String Format
Any sequence of ASCI chars in 0x20-0x7E.
Note: Tabs are forbidden.
Boolean Format
Either "true" or "false".
Note: Lower case only
Unsigned Integer Format
- HEXADECIMAL: numbers with '0x' or '0X' prefix, for example, the following numbers are valid: 0xff, 0xFF, 0Xff, 0XFF, 0xFf
- BINARY: numbers with '0b' or '0B' prefix, for example, the following numbers are valid: 0b110, 0B110.
- DECIMAL: numbers that don't have hexadecimal or binary prefix and don't have leading zeros (e.g. 05). treated as decimal, the following numbers are valid: 123, 0
The integer is in the range [0, 0x7FFFFFFF] (unless mentioned otherwise).
Unsigned Decimal Integer Format
In addition to being an unsigned integer format:
- The number must be decimal (cannot be in HEX/BIN format).
- The integer is in the range [0, 0x7FFFFFFF] (unless mentioned otherwise).
Set Format
- The format is as follows: { item1, item2, ... }
- An example can be found in provided sample file (sample.cong)
Notes:
- 1. Set must start with open-curve-bracket: '{'
- 2. Set must end with close-curve-bracket: '}'
- 3. Set must contain at least one item
- 4. Whitespaces (space and tab) are ignored during the parse process.
- 5. The same item cannot appear more than once (set).
1 <= setSize <= 50 (unless mentioned otherwised)
1 <= charLength <= 800 (unless mentioned otherwised)
Set of Unsigned Integers Format
Each item/integer is in unsigned integer format
Each item/integer is in the range [0, 0xFFFFFFFF] (unless mentioned otherwised)
For example: { 83, 0x3Fa1, 0B101 }
Set of Unsigned Decimal Integers Format
Each item/integer is in unsigned decimal integer format
Each item/integer is in the range [0, 0xFFFFFFFF] (unless mentioned otherwised)
For example: { 1, 16, 35 }
UUID Format
A string of the following format:
[8 digits]-[4 digits]-[4 digits]-[4 digits]-[12 digits]
where a digit is a char in [0-9,A-F,a-f].