| Target Support Package™ TC2 | |
c280xdspchiplib, c281xdspchiplib, and c2833xdspchiplib in Target Support Package TC2 software
The Idle Task block, and the subsystem to which it is connected, specify one or more functions to execute as background tasks. By definition, all tasks executed through the Idle Task block are of the lowest priority, lower than that of the base rate task.
The output of this block includes a set of two vectors, the Number of tasks and the corresponding Preemption flag(s). The Preemption flag(s) vector must be the same length as the Number of tasks vector unless it has only one element.
If the Preemption flag(s) vector does have one element, then that value applies to all functions in the downstream subsystem.
If the Preemption flag(s) vector has the same number of elements as the Number of tasks vector, then each task's preemption flag value is the value of the corresponding element in the Preemption flag(s) vector.
The preemption flag determines whether a given interrupt is preemptable or not. Preemption overrides prioritization, such that a preemptable task of higher priority can be preempted by a non-preemptable task of lower priority.
The values you enter determine the order in which the functions in the downstream subsystem are to be executed, while the number of values you enter corresponds to the number of functions in the downstream subsystem.
Enter a vector containing the same number of elements as the number of functions in the downstream subsystem. This vector can contain no more than 16 elements, and the values must be from 0 to 15 inclusive.
The value of the first element in the vector determines the order in which the first function in the subsystem will be executed, and so on.
For example, if you enter [2,3,1] in this field, you are indicating that there are three functions to be executed, and that the third function will be executed first, the first function will be executed second, and the second function will be executed third.
When all functions have been executed, the Idle Task block cycles back and repeats the execution of the functions in the same order.
The preemption flag determines whether a given interrupt is preemptable or not. Preemption overrides prioritization, so if you flag one of these functions as non-preemptable, its execution will not be suspended by another task even though the functions in the downstream subsystem all have the lowest priority by definition.
Enter either a vector of one element, in which case that preemption flag applies to all functions to be executed in the downstream subsystem, or a vector containing the same number of elements as the Number of tasks vector, in which case each preemption flag values applies to the task number in the corresponding position within its vector. All preemption flag values must be either 0 (non-preemptable) or 1 (preemptable).
Select this check box to make it possible to test asynchronous interrupt processing in the context of your Simulink model.
Note Using this check box is the only way you can test asynchronous interrupt processing behavior in Simulink. |
C280x/C28x3x Hardware Interrupt, C281x Hardware Interrupt
| From RTDX | Integer part IQN | |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |