Description of the life cycle states of a task.
|Configuration and execution||Description|
|Not_ready||This task is not ready for reconfiguration, because its predecessors are not completely reconfigured.|
|Ready||This task is ready for reconfiguration and competes with the other Ready task for the access to the ICAP. Only tasks without predecessors, or whose predecessors have already been reconfigured, can enter this state.|
|Config||The task is under configuration/loading via the ICAP/the communication infrastructure onto the RAMPSoC. If a task with higher priority becomes Ready, the reconfiguration/loading process is terminated/interrupted, and the task returns into the Ready state and waits for a new possibility to access the ICAP/communication infrastructure.|
|Exec||After successful configuration/loading, the task starts execution and enters this state. An execution cannot be interrupted.|
|Exit||After the execution, the task enters this state. The allocated processing element is now free for the next task.|