Visible to Intel only — GUID: GUID-35AE07C5-71D6-48F3-98A2-AA83F373E33A
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-35AE07C5-71D6-48F3-98A2-AA83F373E33A
Emulauncher
During the development of your trusted application you will want to develop and test the application without the need for a silicon-based machine. For this purpose there is an emulator of the Intel® DAL virtual machine (VM). In addition, the emulation has capabilities that will enhance the development experience, including debug prints and source level code debugging.
The Intel DAL Emulauncher tool is responsible for running the emulation over sockets and the matching Intel® DAL Host Interface Service (Intel® DAL HIS).
The tool allows you to switch between different API level emulations and monitor your virtual machine while testing your trusted application. Any changes in your emulation environment are displayed in Emulauncher.
Emulauncher can be run manually, by GHA, Eclipse plugin or Microsoft Visual Studio* plugin, when running an emulated environment, i.e., not real hardware.
Note: In the first release of the SDK, the Emulauncher can emulate API levels 7 and later. API levels 1 through 6 will be supported in a future SDK release.
The behavior of the Intel DAL Emulauncher module is as follows:
- When you click the Run button, the Intel DAL HIS (JHI) is launched. Shortly afterwards, the Intel DAL emulation is launched.
- When you click the Stop button, or when the Intel DAL Emulauncher program is closed, the Intel DAL emulation and the Intel DAL HIS application are terminated.
Android*: There is currently no emulation for Android development.
Main Window
The Emulauncher main window provides a dashboard view of all emulation information. The main window has three buttons and three panes.
Panes
- DAL Emulation Environment: Display of the firmware emulation status, API level, platform, and Intel DAL HIS status.
- DAL Emulation Monitor: Real time log of VM status - loaded trusted applications and opened sessions list.
- Extended Info: Details of additional information. Selecting a trusted application displays its UUID, vendor and name or description. Selecting a session displays its application path and Process ID (PID).
Functions
- Start/Stop Emulation: Control emulation
- Settings: Configure emulation settings
- Troubleshoot: Open Intel DAL Troubleshooter
Note: Starting/stopping emulation when running over HECI may take a few minutes.
Emulauncher Settings
When running the Intel DAL Emulauncher in the default sockets option, you can choose between three emulator run options:
- API Level - Run the emulation according to the API level you are developing for, independent to the platform type or version. The tool will select the best emulation available for this API level.
- Platform - Select the emulation according to the platform type and version.
- Custom - Any executable you wish to run. This option enables you to run old versions of emulation you may want to run in order to reproduce status.
Warning: The Emulauncher Settings window will not open while emulation is running.
You can also choose to:
- Clear flash data. This setting clears the flash and starts with the base FW image rather than continuing with the previously run flash image. The flash data stores values such as a trusted application's flash storage, monotonic counter value and FW related data.
- Restart emulation each time you click Start Emulation. If you do not choose to restart emulation each time you click Start Emulation and you try to run a different platform from Eclipse or Microsoft Visual Studio you will get a notification that a different version is already running, and that you should close the running emulation before trying to start a new version.
- Run in an emulation only mode in which the Intel DAL HIS will not be installed and run. This mode is useful when connecting to emulation from a remote Linux host platform.
- Enable OEM Signing. This flag allows you to load S-SDs on the emulation. See details in OEM Signing.
- Profile Trusted Application heap usage. This setting should only be used at the specific time the heap memory profiling is wanted. This setting is not saved from session to session if Emulauncher is closed. The feature supports multiple sessions and the history of each trusted application is saved, unless the Clear History function is used. Select a trusted application from the Profiler list to view its history.
VM Monitor
The VM monitor allows you to monitor the virtual machine. All installed trusted applications are displayed. For each trusted application you can see all its sessions and the application that opened each session. For each session you can see all the owners. If a session was left open while the owner process was closed, the session will be marked as an orphan.
Note: This feature is supported from API Level 4 and above.
Did you find the information on this page useful?
Feedback Message
Characters remaining: