IPC@CHIP Documentation - SC12 @CHIP-RTOS V1.10

Suspended Free to run RTX_Resume_Task() → Active
Trigger Wait 1 RTX_Resume_Task() → Blocked
RTX_Restart_Task() → , Free to run 3
Semaphore Wait 2 RTX_Resume_Task() → Blocked
Granted semaphore → , Free to run 3
Event Group Wait 2 RTX_Resume_Task() → Blocked
RTX_Signal_Events() → , Free to run 3
Message Exchange Wait 2 RTX_Resume_Task() → Blocked
RTX_Send_Msg() → , Free to run 3
Asleep2 RTX_Resume_Task() → Blocked
RTX_Wakeup() → , Free to run3 1) - Trigger Wait sub-state is entered after RTX_Create_Task_Without_Start() or after a task has
terminated.
2) - A specified time-out period in milliseconds can be applied to these states.
3) - Only the sub-state has changed here.
Table 2 ) @Chip-RTOS Task States
The set of active tasks we speak of as executing concurrently. However, only a single task (at most 1 ) is
executing at any given time since the IPC@Chip contains only a single CPU. The task selected for
execution by the @Chip-RTOS will always be the highest priority of the tasks that are in the active state.
The C-library routines which force a task to exit the Blocked and Suspended states when called by some
other task or Interrupt Service Routine (ISR) are stated in the table. The two inactive states, Blocked and
Suspended, differ in their exit state transitions. The RTX_Suspend_Task() API transitions a task into the
Suspended state.
1 Hardware interrupt service routines can momentarily suspend the executing task.
Top of this document
IPC@CHIP Documentation Index
DOS Program Tasks
Each DOS program is launched as a task under @Chip-RTOS. These tasks are created with initial priority 25
and time-slicing disabled. Within these DOS programs, users can create additional tasks with the
RTX_Task_Create() or RTX_Task_Create_Without_Run() API
System Timing
The @Chip-RTOS uses a 1000 Hz Real-Time Interrupt (RTI) for its time base. Therefore one millisecond is the
lower resolution available for task timing.
Users can install Timer Callback procedures with the RTX_Install_Timer() API. Your callback procedure is
invoked within the top priority kernel task at a specified interval
Page 223 / 400