Defining the Scheduling (RTA-OSEK + Generic OSEK)

Note

This instruction is valid for a target with RTA-OSEK or GENERIC-OSEK operating system.

  1. In the Scheduling combo box, assign one of three possible scheduling modes to the task.

    Note

    This option is not available for init and interrupt tasks.

    The following modes are available:

    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.

    Note

    The use of COOPERATIVE tasks is not recommended for ASCET‑SE projects.

FULL and NON tasks share a common priority region. Cooperative tasks have their own priority region below FULL and NON tasks. See also Task Priorities.

See also

Task Priorities

Selecting the Task Type

Assigning a Priority

Defining the Scheduling (Generic OS)

Selecting a Trigger (ISR Source)

Setting Period, Delay, and Max. Number of Activations

Setting the Autostart Option

Setting Up Hook Routines