Visible to Intel only — GUID: GUID-C6DBF0BE-A0C7-4114-A921-DA974B3DF839
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
Source Level Debugging
Connecting to an Already Running Session
Preparing and Submitting Your Project for Signing
Signing an Applet
Signing New Versions
Visible to Intel only — GUID: GUID-C6DBF0BE-A0C7-4114-A921-DA974B3DF839
Debugging Trusted Applications
Debugging the source code of your trusted application is available only when the trusted application is executed in the emulation environment.
Before you can debug a trusted application, it must be built and packaged for debugging. In Eclipse*, when you click the Build and Package DAL Project button in the Intel® DAL menu, the dialog that opens has a checkbox For Debugger. Select this option when building and packaging.
Notes: • The resulting package is Workspace\ProjectName\bin\ProjectName -debug.dalp. Be sure to change the trusted application path in your host software accordingly. • When packaging for debug, the open session is delayed for 20000 msec to enable the debugging of the onInit function as well. • The Applet.debugger.timeout property in the manifest defines the timeout of the debugger in milliseconds.
Source Level Debugging
When debugging a project, all regular Eclipse debugging options are available in an emulated environment. All of the output is viewable in Microsoft Visual Studio*, Eclipse and Intel DAL Generic Host Application console panes.
The output display and source level debugging are relevant only when running a trusted application in an emulated environment.
- Insert a breakpoint at the desired location in your trusted application.
- In Eclipse, click Debug.
Eclipse packages your application for debugging, launches Emulauncher and executes your selected run option. When the line with the breakpoint is called, you are asked to switch to Debug Perspection. Click Yes.
Now you can debug as usual.
Connecting to an Already Running Session
If you already have a session open, you can connect to it. Place a breakpoint in the desired location and click DAL ► Connect to DAL Debugger (or click the Connect to DAL Debugger button (). Eclipse will automatically switch to Debug Perspective and you will be able to debug as usual.
Note: To debug the onInit function, you need to click DAL ► Connect to DAL Debugger immediately after the host application performs the open session of the trusted application.