Task Options
Note |
|---|
This topic is irrelevant for the EHOOKS target or the ANSI-C target with RTE-AUTOSAR * operating system. |
The options of a selected task are shown on the right-hand side of the OS tab. Depending on the OS selected in the Build node of the project properties, different task options are available.
RTA-OSEK + Generic-OSEK (ASCET‑SE targets and ASCET‑RP targets ES910 and RTPRO-PC)
Type
Determines the task type. Possible values are:
Alarm | Periodic task, triggered once at the beginning of each interval defined in the Period field. |
Init | Triggered only once at the startup of the assigned application mode. |
Software | Triggered by operating system commands. |
Interrupt | Triggered by hardware events. |
Priority
Note |
|---|
Available for alarm tasks, software tasks and interrupt tasks. |
Task priority; determines the activation sequence. A higher number means higher priority.
Scheduling
Note |
|---|
Available for alarm tasks and software tasks. |
Scheduling mode. Possible values are:
FULL | Full preemptive scheduling. A running task with mode FULL is interrupted as soon as a task with higher priority is activated. The task context is saved so that the preempted task can be continued at the location where it was interrupted. | ||
NON | Non-preemptive scheduling. A running task with mode NON can be interrupted only at an explicit point of rescheduling, even if a task with higher priority is activated. The lower priority task delays the start of the interrupting task up to the next point of rescheduling. Only ISRs can interrupt NON tasks at any point. | ||
Cooperative | Cooperative scheduling. The lowest priority tasks share the same internal resource; they can be freely interrupted by higher-priority tasks of mode FULL or NON. A higher-priority task of type COOPERATIVE can interrupt the running cooperative task only after the current process is finished.
|
ISR Source
Note |
|---|
Available for interrupt tasks when you are working with ASCET‑SE. |
Determines the event used as trigger for the interrupt task. Available values depend on the selected target.
Period
Note |
|---|
Available for alarm tasks. |
The activation period in seconds or system ticks, depending on your operating system settings.
Resulting Period
Note |
|---|
Available for alarm tasks. |
The period is converted to the next highest integer number of system ticks. This number is displayed in the Resulting Period field, in seconds or system ticks (depending on your operating system settings), and used as period.
Delay
Note |
|---|
Available for alarm tasks. |
Time in seconds or system ticks (depending on your operating system settings) between activation and start of the task.
Resulting Delay
Note |
|---|
Available for alarm tasks. |
The delay is converted to the next highest integer number of system ticks. This number is displayed in the Resulting Delay field, in seconds or system ticks (depending on your operating system settings), and used as delay time.
Max. number of Activations
Note |
|---|
Available for alarm tasks and software tasks when you are working with ASCET‑RP. |
Determines how many times a task can be activated in parallel.
Autostart
Alarm tasks: When activated, the timer for the selected task starts at the initialization of the associated application mode.
Software tasks: The task is executed once at the initialization of the associated application mode.
pre/post hooks
Note |
|---|
Available for alarm tasks, software tasks and interrupt tasks when you are working with ASCET‑RP. |
Determines the way hook routines for debugging purposes are generated. Only useful when Enable Monitoring is activated.
none | no debug functions |
monitoring | complete debug functions |
Generic OS (PC and Prototyping targets)
Type
Determines the task type. Possible values are:
Alarm | Periodic task, triggered once at the beginning of each interval defined in the Period field. |
Init | Triggered only once at the startup of the assigned application mode. |
Software | Triggered by operating system commands. |
Interrupt | Triggered by hardware events. Not available for the PC target. |
Priority
Note |
|---|
Available for alarm tasks, software tasks and interrupt tasks. |
Task priority; determines the activation sequence. A higher number means higher priority.
Scheduling
Note |
|---|
Available for alarm tasks and software tasks. |
Scheduling mode. Possible values are:
cooperative | Periodic task, triggered once at the beginning of each interval defined in the Period field. |
preemptive | Triggered only once at the startup of the assigned application mode. Not available for the PC target. |
Period
Note |
|---|
Available for alarm tasks. |
The activation period in seconds.
Delay
Note |
|---|
Available for alarm tasks. |
Time in seconds between activation and start of the task.
The following options are read-only for the PC and Prototyping targets:
Option name | Available for | Meaning | ||||
|---|---|---|---|---|---|---|
ISR Source | interrupt tasks | Determines the event used as trigger for the interrupt task. Available values depend on the selected target. | ||||
Max. number of Activations | alarm tasks, software tasks | Determines how many times a task can be activated in parallel. | ||||
Autostart | alarm tasks | When activated, the timer for the selected task starts at the initialization of the associated application mode. | ||||
software tasks | The task is executed once at the initialization of the associated application mode. | |||||
Deadline | alarm tasks, software tasks | When activated, two consecutive task activations do not exceed the time in seconds specified in the input field. | ||||
Min. period | interrupt tasks | When activated, two consecutive task activations do not fall below the time in seconds specified in the input field. | ||||
pre/post hooks | alarm tasks, software tasks, interrupt tasks | Determines the way hook routines for debugging purposes are generated. Only useful when Enable Monitoring is activated.
|
See also
Operating System Settings (RTA-OSEK + Generic-OSEK)