The specified procedure
proc will be called based on a timer.
You must call either the RTX_Start_Timer(), RTX_Timer_Delay() or RTX_Timer_Delay_RTI() API to get the kernel to start calling your new timer procedure.
Timers require the use of one general purpose kernel object, of which the system has a total of 1000.
- Timer procedures are executed in a top priority task, so the timer user callback procedure should be as short as possible. Avoid calling time consuming functions. It is not legal to call any API which may block from a timer callback. The system is not protected against such a violation and to do so may cause the system to crash. The total stack space available is ???? bytes, a few of which are used by the system on entry into the callback.
|tag||Up to 4 character name to give timer. Nil terminator is optional. |
|proc||Vector to timer procedure. |
|interval||Timer interval in milliseconds. This value must be non-negative, and when multiplied by the RTI rate must not exceed 31 bits. Otherwise this API will either fail with return value zero or create a timer with an undesired interval (depending on the nature of the count overflow). |
|lParam||Optional 32 bit parameter to pass to timer callback procedure |
- Timer ID (handle) on success, else zero on failure.
- See also
- RTX_NewFineTimerCB() RTX_Remove_Timer()
- This API is not compatible with the SC1x, SC2x and SC1x3 C-library. The legacy function RTX_Install_Timer() may be used when cross system source compatibility is required.