Note:
|
RTAPI function |
Notes |
Deterministic? |
|---|---|---|
|
|
Yes - can block if another thread holds the lock. |
|
|
|
No |
|
|
|
Yes, but only when one real-time processor configured. |
|
|
|
Yes, but only when one real-time processor configured. |
|
|
The call is supported as both an Rt call and as a Windows call (for example, RtAtoi and Atoi). |
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
No |
|
|
The eRTOS IPC namespace is separate from the Windows namespace. |
No |
|
|
The eRTOS IPC namespace is separate from the Windows namespace. |
No |
|
|
|
No |
|
|
The eRTOS IPC namespace is separate from the Windows namespace. |
No |
|
|
|
No |
|
|
|
No |
|
|
|
No |
|
|
|
No |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
No |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
No |
|
|
|
No |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
No |
|
|
|
No |
|
|
|
No |
|
|
|
No |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes |
|
|
|
Yes |
|
|
|
No |
|
|
The call is supported as both an Rt call and as a Windows call (for example, RtAtoi and Atoi). |
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
The priority spectrum of eRTOS is 0 to 127, whereas the Windows range is {-15, -2, -1, 0, 1, 2, 15}. The call is supported as both an Rt call and as a Windows call (for example, RtAtoi and Atoi). |
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
No |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
No |
|
|
|
No |
|
|
The eRTOS IPC namespace is separate from the Windows namespace. |
No |
|
|
The eRTOS IPC namespace is separate from the Windows namespace. |
No |
|
|
|
No |
|
|
The eRTOS IPC namespace is separate from the Windows namespace. |
No |
|
|
|
No |
|
|
|
No |
|
|
The call is supported as both an Rt call and as a Windows call (for example, RtAtoi and Atoi). |
No |
|
|
The eRTOS IPC namespace is separate from the Windows namespace. |
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes, if DumpLevel is 0. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
The eRTOS IPC namespace is separate from the Windows namespace. |
Yes, unless the mutex has a higher priority thread waiting on it. |
|
|
The eRTOS IPC namespace is separate from the Windows namespace. |
Yes, unless the semaphore has a higher priority thread waiting on it. |
|
|
|
No |
|
|
The eRTOS IPC namespace is separate from the Windows namespace. |
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes |
|
|
|
No |
|
|
|
No |
|
|
The eRTOS IPC namespace is separate from the Windows namespace. |
Yes, unless the event has a higher priority thread waiting on it. |
|
|
|
Yes |
|
|
The call is supported as both an Rt call and as a Windows call (for example, RtAtoi and Atoi). |
Yes |
|
|
The priority spectrum of eRTOS is 0 to 127, whereas the Windows range is {-15, -2, -1, 0, 1, 2, 15}. The call is supported as both an Rt call and as a Windows call (for example, RtAtoi and Atoi). |
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
No |
|
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
|
No |
|
|
|
No |
|
|
|
No |
|
|
RtWaitForMultipleObjects |
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
Yes - the elapsed time for the call is less than 5 microseconds. |
|
|
The call is supported as both an Rt call and as a Windows call (for example, RtAtoi and Atoi). |
No |
|
|
The call is supported as both an Rt call and as a Windows call (for example, RtAtoi and Atoi). |
Yes - the elapsed time for the call is less than 5 microseconds. |
About #pragma deprecated Functions in Rtapi.h
The functions listed under #pragma deprecated in the real-time API, Rtapi.h, are actually unsupported, not deprecated. Listing them this way ensures that a warning appears in Visual Studio when a developer attempts to use an unsupported function in Visual Studio.
