This section describes properties of the MQXLite_task component. The MQX Lite task template list is generated based on the settings in this component.
- Name - String name for the task.
- Entry point function - Root function name for the task. This function is called when the task is created. It's up to the user to implement this function (in mqx_task.h/.c by default).
- Stack size - Size of the stack space required by the task.
- Priority - Software priority of the task. Priorities start at 0, which is the highest priority. 1, 2, 3, and so on, are progressively lower priorities. Due to mapping of task priority levels and interrupt levels on some microcontroller platforms, it is recommended to start assigning the priorities at number 7 for the highest-priority task.
- Creation parameter - The value stored in this property is the default value that is passed as the creation parameter to the task when created.
- Attributes - Enables/disables task attributes relevant for the selected platform.
- MQX_AUTO_START_TASK - When MQX Lite starts, it creates one instance of the task and makes it ready.
- Settings supported for Freescale ColdFire and ColdFire+ derivatives only. MQX_DSP_TASK - MQX Lite saves the DSP coprocessor registers as part of the task's context. If the DSP registers are separate from the normal registers, MQX Lite manages their context independently during task switching. MQX Lite saves or restores the registers only when a new DSP task is scheduled to run.
- MQX_FLOATING_POINT_TASK - Task uses the floating point co-processor. MQX Lite saves floating-point registers as part of the task's context.