Linux Task

R2026b

Spawn task function as separate Linux thread

• 

Linux Task block

To add a block to a model, double-click the canvas and start typing the block name. Then, select the block from the list.

Libraries:
SoC Blockset Support Package for AMD FPGA and SoC Devices

Description

Add-On Required: This feature requires the SoC Blockset Support Package for AMD FPGA and SoC Devices add-on.

Use this block to create a task function that spawns as a separate Linux^® thread. The task function runs the code of the downstream Function-Call Subsystem (Simulink) block.

Examples

Get Started With Code Generation Using SoC Blockset Support Package for AMD SoC Devices

Generate code from a Simulink model and run the executable on an AMD^® Zynq^® board.

• Open Live Script

Ports

Output

Port_1 — Function-call control signal

scalar

A function-call control signal that triggers a Function-Call Subsystem (Simulink) block.

Parameters

To edit block parameters interactively, use the Property Inspector. From the Simulink^® Toolstrip, on the Simulation tab, in the Prepare gallery, select Property Inspector.

To set the block parameter value programmatically, use the set_param (Simulink) function.

To get the block parameter value programmatically, use the get_param (Simulink) function.

Task Name — Name of thread on Linux

Task0 (default) | character vector

Assign a name to this task. You can enter up to 32 letters and numbers. Do not use standard C reserved characters, such as the / and : characters.

Programmatic Use

Block Parameter: taskName

Thread scheduling policy — Thread scheduling policy used by Linux

SCHED_FIFO (default) | SCHED_OTHER

Select the scheduling policy that applies to this thread. You can choose from these options:

• SCHED_FIFO — This option enables a first-in, first-out (FIFO) scheduling algorithm that executes real-time processes without time slicing. With FIFO scheduling, a higher-priority process preempts a lower-priority process. The lower-priority process remains at the top of the list for its priority and resumes execution when the scheduler blocks all higher-priority processes.

  For example, in the FIFO scheduling image, task2 preempts task1. Then, task3 preempts task2. When task3 completes, task2 resumes. When task2 completes, task1 resumes.

  

  Selecting SCHED_FIFO displays the Thread priority parameter, which you can set to a value from 1 to 99.

• SCHED_OTHER — This option enables the default Linux time-sharing scheduling algorithm. You can use this scheduling for all processes except those requiring special static priority real-time mechanisms. With this algorithm, the scheduler chooses processes based on their dynamic priority within the static priority 0 list. Each time the process is ready to run and the scheduler denies it, the operating system increases the dynamic priority of that process. Such prioritization helps the scheduler serve the SCHED_OTHER processes.

  Selecting SCHED_OTHER hides the Thread priority parameter and sets the thread priority to 0.

Programmatic Use

Block Parameter: taskPolicy

Thread priority — Linux thread priority

1 (default) | 1 .. 99

Specify the priority of the Linux thread. A value of 1 indicates a low priority, and a value of 99 indicates a high priority. Higher-priority tasks can preempt lower-priority tasks.

To enable this parameter, set Thread scheduling policy to SCHED_FIFO.

Programmatic Use

Block Parameter: taskPriority

Version History

Introduced in R2013a