Main Content

Task Manager

Create and manage task executions in Simulink model

expand all in page
  • Task Manager block

Libraries:
SoC Blockset / Processor Task Execution
C2000 Microcontroller Blockset / Scheduling
Embedded Coder Support Package for Infineon AURIX TC3x Microcontrollers / Scheduling
Embedded Coder Support Package for Infineon AURIX TC4x Microcontrollers / Scheduling

Description

The Task Manager block simulates the execution of software tasks as they would be expected to behave on an SoC processor. With the Task Manager, you can add and remove tasks from your model that can either be timer-driven or event-driven. Tasks can be represented in a model as rates, for timer-driven tasks, or function-call subsystems, for event-driven tasks, contained inside a single Model block. The Task Manager executes individual tasks based on their parameters, such as period, duration, trigger, priority, or processor core, and the combination of that task with the state of other tasks and their priorities in the running model.

In simulation, this block uses code generation to improve simulation speed. This entails some overhead when first simulating, but subsequent simulations are faster if the block settings remain unchanged. For more information, see Interpreted Execution vs. Code Generation.

Note

The Task Manager block cannot be used in a referenced model. For more information on referenced models, see Model block.

The Task Manager block provides three methods to specify the duration of a task in simulation:

  • A probability model of task duration defined in the block mask.

  • From a data file recording of either a previous task simulation or from a task on an SoC device.

  • Input ports on the block, which you can connect to more dynamic models of task duration.

Examples

Timer-Driven Task

Timer-Driven Task

Use the Task Manager block in a simple system where a timer-driven task samples and modifies data generated from a random number source.

(SoC Blockset)

Event-Driven Task

Event-Driven Task

Use the task manager block to a simple system where data from UDP source gets processed asynchronously each time a data packet arrives. The task manager block

(SoC Blockset)

Task Execution

Task Execution

Simulate task execution and how to generate code and run it on an SoC hardware board.

(SoC Blockset)

Limitations

Ports

Output

expand all

A function-call signal that can trigger timer-driven and event-driven tasks, represented as rate or function-call subsystems in the processor Model block, respectively.

For a rate port from a timer-driven subsystem, to show on the Model block, set the Block Parameters > Main > Schedule rates and select ports. For a function-call port from an event-driven subsystem contained in a Function-Call Subsystem block to show on the Model block, include an Inport in the processor Model block connected to the function-call trigger port of the subsystem. In the Inport, check Block Parameters > Signal Attributes > Output function call.

Note

The Task1 port must be connected to either a function-call port or scheduled rate signal port on a Model block.

Dependencies

To create or remove a control signal port for a task, add or remove the task from the Task Manager block by clicking the Add or Delete buttons in the block dialog mask.

Input

expand all

A message port that triggers the associated event-driven task. The Task1Event port receives the message from Event Source block. For more information on messages, see Messages.

Dependencies

To show a Task1Event port, then Task1 must have Type set to Event-driven.

Data Types: rteEvent

A positive value signal that specifies the execution duration of a task at the present time. For more information on specifying task duration, see Task Duration (SoC Blockset).

Dependencies

To enable this port, set the Specify task duration via parameter to Input port.

Data Types: single | double | int8 | int16 | int32 | uint8 | uint16 | uint32

Parameters

expand all

Enable or disable the simulation of task duration. If you clear this parameter, tasks simulate using a function-call generator inheriting their period from the fundamental sample time of the model for event-driven tasks or from the dialog for timer-driven tasks.

List of the tasks generated by the Task Manager block. Each task has a set of parameters listed in the Main and Simulation tabs of the block dialog mask.

Add a task to the Task Manager block. During deployment, each task is encapsulated as an execution thread in the generated code. The properties of the thread are taken from the Main parameters for that task. During simulation, the task uses a combination of the Main and Simulation parameters for that task.

Remove a task from the Task Manager.

Dependencies

To enable this parameter, specify at least two tasks.

Use the Schedule Editor to specify the ordering of the tasks in the SoC model. When using the Schedule Editor, task priority is automatically assigned to the tasks based on their order in the editor and the base rate priority of the processor model.

Main

Unique name of the task. The task name must only contain alphanumeric characters and underscores.

Specify the task as timer-driven or event-driven. For more information on timer- and event-driven tasks, see Timer-Driven Task (SoC Blockset) and Event-Driven Tasks (SoC Blockset), respectively.

Dependencies

To enable this parameter, set Type to Timer-driven.

Specify the trigger time period for timer-driven tasks.

Specify the number of the processor core where a task executes. .

To have the operating system dynamically assign a core to the task, set this value to -1.

Specify the schedulers priority for the event-driven task between 1 and 99. Higher priority tasks can preempt lower priority tasks, and vice versa. The task priority range is limited by the hardware attributes. For more information on task priority, see Task Priority and Preemption (SoC Blockset).

Dependencies

To enable this parameter, set Type to Event-driven and Use Schedule Editor ordering to off.

Select this parameter to force tasks to drop, rather than catch up, following an overrun instance. For more information on task overruns, see Task Overruns and Countermeasures (SoC Blockset).

Note

No more than 2 instances of a task can overrun execution when Drop tasks that overrun is set to off. Any additional task instances that overrun drop automatically.

Simulation

Select this parameter for the Task Manager block to play back the recorded execution data provided from the specified File name parameter. For more information on replaying task execution, see Task Execution Playback Using Recorded Data (SoC Blockset).

Specify the source of the timing information for the task execution.

  • Dialog - Use a normally distributed probabilistic model with Mean, Deviation, Min, and Max defined in the block dialog mask.

  • Input port – When set from Input port, the block input port dynamically defines the execution duration.

  • Record task execution statistics – Use a normally distributed probabilistic model with mean and deviation provided in file specified by File name.

For more information on configuring task duration, see Task Duration (SoC Blockset).

Task duration settings

Adds a distribution to the set of normal distributions that generates an execution duration.

Note

Only a maximum five distributions can be assigned to a single task.

Remove a distribution from the set of normal distributions.

Specify the likelihood of each normal distribution. The Percent weighted sum of normal distributions determines the task duration likelihood.

Note

The sum of Percent for all the distributions in a single task must equal 100.

Specify the mean duration of the task during simulation of the task. The simulated task duration uses a normal distribution with a specified Mean and SD parameter values as a first-order approximation of the task behavior.

Specify the standard deviation duration of the task during simulation of the task. The simulated task duration uses a normal distribution with a specified Mean and SD as a first-order approximation of the task behavior.

Lower limit of a task duration distribution.

Upper limit of a task duration distribution.

The data in this file specifies the Mean and SD parameter values. When the Play recorded task execution sequence parameter is selected, the specified CSV file provides the explicit task execution timing. The CSV file contains the diagnostic data of the task scheduler previously recorded from the hardware board.

Dependencies

To enable this parameter, set the Specify task duration via parameter to Recorded task execution statistics.

Extended Capabilities

Version History

Introduced in R2019a

See Also

(SoC Blockset) | (SoC Blockset)

Topics