This section describes properties of the MQX Lite component. Properties are parameters of the component that influence the generated code. See the Processor Expert User Guide for more details.
- Component name - Name of the component.
- MQX Lite version - Specifies which MQX Lite version is used. It affects which MQX Lite source files are copied into the project.
- Copy source files to project - Specifies whether MQX Lite source files are copied into a project after code generation.
- System timer - System timer is used for kernel notification (for details about settings see Component Inheritance & Component Sharing).
- Task Template List - The task template list is an array of task template structures terminated by a zero-filled element. The MQX Lite initialization structure contains a pointer to this list.
- Configuration parameters - MQX Lite configuration parameters.
- Components - MQX Lite components (LW Semaphores, Mutexes, LW Events, LW Message Queues, Logs, and Memory Allocation) settings.
- Lightweight Semaphores - Specifies whether Lightweight Semaphores are allowed in an MQX Lite project. As LW Semaphore is a core required component disabling this option is not recommended.
- Lightweight Events - This property specifies whether Lightweight Events can be used in an MQX Lite project.
- Lightweight Message Queues - This property specifies whether Lightweight Message Queue can be used in an MQX Lite project.
- Mutexes - This property specifies whether Mutexes can be used in an MQX Lite project.
- Lightweight Timer - This property specifies whether Lightweight Timer can be used in an MQX Lite project.
- Kernel logging - This property specifies whether Kernel Logging is allowed in an MQX Lite project.
- Lightweight Memory Allocation - This property specifies whether Lightweight Memory Allocation is allowed in an MQX Lite project.
- Interrupts - Interrupt settings.
- Interrupt stack size - Size of the stack space used by all ISRs.
- Idle Task - Idle Task settings.
- Use Idle Task - When enabled, the kernel creates the idle task; otherwise, if a task is not ready, it does not run. The use of an idle task is mandatory for Kinetis platforms.
- Enable sleep in idle - Enables the use of the WFI (wait for interrupt) instruction in the idle task loop.
- User settings - User settings.
- Definitions - Other user defined values placed into the user_config.h.
- Components - MQX Lite components (LW Semaphores, Mutexes, LW Events, LW Message Queues, Logs, and Memory Allocation) settings.
- Manage allocated interrupts - This property specifies the range of used interrupt vectors. The range can be specified automatically or manually by user. This influences the size of the MQX Lite interrupt table.
The following items are available only if the group is enabled (the value is "By user"):
- First allocated interrupt - First user allocated interrupt vector can be chosen from the list.
- Last allocated interrupt - Last user allocated interrupt vector can be chosen from the list.
- MQX functions - Contains the RTOS specific settings. The settings in this section are common for all components generally called RTOS Adaptors. The MQX Lite component is a special kind of RTOS Adaptor, which makes the code generated by all other PEx components compatible with MQX Lite.
- Critical section - Definition of the RTOS API which provides the critical section handling for HAL driver code.
- User function for entering critical section - The open critical section function should introduce the code which cannot be interrupted by the ISRs. This function can be also called from ISRs and/or within a context where ISRs are already disabled.
In this situation the function has no effect (except that the pair call to critical section close function is also ignored - see property "User function for exiting critical section"). The function has no parameters and returns no value.
The following item is available only if the group is enabled (the value is "yes"):
- User function for entering critical section - The open critical section function should introduce the code which cannot be interrupted by the ISRs. This function can be also called from ISRs and/or within a context where ISRs are already disabled.
In this situation the function has no effect (except that the pair call to critical section close function is also ignored - see property "User function for exiting critical section"). The function has no parameters and returns no value.
- User function name - The name of the user function (see above for description).
- Critical section - Definition of the RTOS API which provides the critical section handling for HAL driver code.
- User function for exiting critical section - The close critical section function should terminate the code which cannot be interrupted by the ISRs.
This function should always have a pair call to the open critical section (see property "User function for entering critical section"). If the call to the pair open critical section was ignored, the respective close should be also ignored. The function has no parameters and returns no value.
The following item is available only if the group is enabled (the value is "yes"):
- User function name - The name of the user function (see above for description).