Intel® Dynamic Application Loader (Intel® DAL) Developer Guide
Visible to Intel only — GUID: GUID-169B7E0F-02AE-47FF-9022-AE84EE0D9081
Visible to Intel only — GUID: GUID-169B7E0F-02AE-47FF-9022-AE84EE0D9081
Running Your Project
The running of a trusted application is done from a host application. Running is possible only after:
- The trusted application has been downloaded into a machine, either as an emulation or silicon-based.
- The trusted application instance is open.
- There is a communication channel, or session, with a host software.
This flow requires the host software to call the Intel® DAL Host Interface Service functions:
- Install
- Create session
- Send and receive
- End session
- Uninstall
Real-world host applications perform many other actions, e.g., login, before calling the Intel DAL Host Application Service send and receive function. For those just starting out with the Intel DAL development process and for trusted application test purposes, there is a use for a generic host application that calls only the Intel DAL Host Interface Service functions with no other logic to allow users to begin running and testing their trusted applications. For this there is the Generic Host Application tool. The SDK in Intel DAL contains plugins to the Eclipse* and Microsoft Visual Studio* IDEs to make the run process easier and more intuitive.
Running via Eclipse*
When using the Intel DAL project wizard to create a trusted application, it provides the ability to create a host application with the basic functions above. Eclipse also packages your trusted application; launches the Intel DAL emulation tool, Emulauncher and opens Microsoft Visual Studio.
In Eclipse, select Run ► DAL Launch.
The Eclipse Console window displays the application progress.
Running via Microsoft Visual Studio*
Projects created with the SDK have a build configuration named Amulet which enables running of Intel DAL projects on emulation.
When you want your application to run on emulation, select the Amulet build configuration.
When you want it to run on a silicon-based machine, select any other build configuration, i.e., Debug or Release.
In Microsoft Visual Studio, select your desired configuration (Amulet, Debug, or Release)and click Start Debugging (F5).
- If you selected Amulet as your build configuration, Emulauncherhttp://developers.txe.iil.intel.com/sdk/contents/emulauncheropens and you must approve the User Access Control query that opens. Then continue debugging as usual.
- If you selected any other build configuration, debug as usual.
You can see the output of the trusted application in the Microsoft Visual Studio Output window by selecting Amulet from the drop down list. If your Microsoft Visual Studio Output window is closed, you can open it by clicking View ->Output.
See the Generic Host Application for an example of representative host functionalities when running trusted applications.