Visible to Intel only — GUID: GUID-663834D2-E26E-40D9-918F-CCFF9A4C4F92
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
Creating the Downloadable Package
To create a downloadable package:
Custom Build Scripts
Changed version of the files in a separate location
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-663834D2-E26E-40D9-918F-CCFF9A4C4F92
Building and Packaging Your Project and Running in Emulated Environment
Before your trusted application can be downloaded and installed into the trusted environment, it must be packaged. The packaging process is done by the Intel® DALjde Eclipse* plugin.
Creating the Downloadable Package
To create a downloadable Intel® DAL package, you need to perform the following steps:
- Compile the code to .class files.
- Create the .jeff file.
- Run the pack tool. This creates the Intel DAL package with all the information and structure necessary for the package to be downloadable and runnable on the Intel® Management Engine (Intel® ME) virtual machine.
- (In Intel DAL API Level 1.1 and higher projects) Create the .dalp file from the package file.
These steps are done automatically by the Intel DALjde Eclipse plugin. The developer does not need to take the trusted application files through this process manually.
To create a downloadable package:
- With the focus on the required project, choose DAL > Build and Package DAL Project, or click the Build and Package DAL Project button.
- The Packaging Intel DAL Trusted Application window opens with information about the application pack to be created.
- For projects for Intel DAL API Level 1.1 and higher, there is a For Debugger option that determines whether the trusted application will be compiled and packaged as a regular trusted application or in a form that will allow source-level debugging. Select this option if you will be doing source-level debugging.
- Click OK. The Intel DAL packager starts to create the package.
The Intel DAL Build Console displays the progress of package creation. When the process completes, the packaging function displays a message box indicating success or failure. In a multiple platform environment where one or more packages are being created, the message box indicates a success or failure for each platform.
By default, the packaging function first creates an Apache Ant* command file (.xml) for each API level and then runs it. The function saves each of these files in the project directory's Build Scripts folder so that it can be re-used externally for automated build procedures.
Custom Build Scripts
By default, the Intel DALjde Eclipse plug-in builds Intel DAL projects using a predefined chain of operations. The default build script is based on the Apache Ant build framework integrated into Eclipse. The plugin builds a project by generating an Apache Ant file dynamically at build time. This file is based on a template and modified to reflect the values and parameters of the project being built.
Changed version of the files in a separate location
In order to provide for specialized build-chains for a specific project, the SDK provides the ability to specify a per-project build script. This can be either Ant based or script (.cmd file) based.
In order to specify a specialized build script place one of the following files in the project directory (e.g. in MyEclipseWorkspace\myProject):
- DALBuild.ant.template Apache Ant based
- DALBuild.cmd.template script (.cmd) based
The scripts can make use of the file containing a list of all .java and .jar files in the project. The filename of this file is represented by the macro CLASS_FILES_ LIST. The output of this process must be a <project name>.dalp (or <project name>.pack for API Level 1) file in the project's\bin directory.