Visible to Intel only — GUID: GUID-EDC9C22B-FD9E-4092-A38F-CF8E60E0AECF
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-EDC9C22B-FD9E-4092-A38F-CF8E60E0AECF
Timer Guidelines
This page provides details on how to use timers in Intel® DAL. For an overview of what timers do, see Timers.
Timer is an object of class com.intel.util.TimerManager.Timer. Timer becomes a "running timer" when an instance of com.intel.util.TimerManager.Timer is created and started by Timer.start(int, byte[], int, int, boolean).
Known Issues
- It is strongly recommended to not use Timer.start(…) inside TimerClient.onTimerTick(…) call back for the same timer instance. For example:
class Applet implements IntelApplet, TimerClient{
Timer m_timer =
TimerManager.getInstance().create(this);
void invokeCommand(int cmd, byte[] bfr){
m_timer.start(…);
}
void onTimerTick(byte[] bfr){
m_timer.stop();
m_timer.start(…); //not recomended
}
}
This not recommended use may lead to UtilOutOfResourcesException during the Timer.start(…), the reason for that is by design of the Java* timers by Native timers sub-system.
- OutOfMemoryError during Timer.start(..)
During Timer.start(…) call, the VM is allocating and releasing memory on the trusted application's heap memory. If the trusted application's heap is full, an OutOfMemoryError will be thrown.
Performance
It is not recommended to start a cyclic timer with a low tick value. Timer works in a resolution of a tick (1 tick = 1 millisecond). No restrictions are present to start a timer with a low tick value. Using (periodic) timers with a low tick count, will result in Intel DAL processing a lot of timer expirations in a short time, and it will affect overall responsiveness of the system. Also, since there's processing overhead of handling such timers, the expiration callbacks are most likely to be called with a considerable delay (relative to the tick-count). E.g.: for a timer scheduled to expire in 10 milliseconds, the callback might be called after 12 milliseconds (20% difference), whereas if the timer was scheduled to expire in 1 second, and the callback is called after 1.002 seconds, the impact is relatively low.