Priority of event code is not supported for Kinetis and ColdFire+.
You can also select a priority for the processing of the event code. This setting is available for the events that are invoked from the Interrupt Service Routines. This priority may be different from the interrupt priority. However, the meaning of the number is same, the event may be interrupted only by the interrupts with the higher priority. Processor Expert offers the following architecture independent values:
- same as interrupt - default value which means that Processor Expert does not generate any code affecting the priority of the event; the priority is in the state determined by the default hardware behavior.
- minimum priority
- low priority
- medium priority
- high priority
- maximum priority
- interrupts disabled - For example, the highest priority supported by the microcontroller, which may be interrupted only by non-maskable interrupts.
The selected value is automatically mapped to the priority supported by the target microcontroller and the selected value is displayed in the third column of the
Component Inspector.
Refer to the version specific information below. You may also select a target-specific value, if portability of the application to another architecture is not required.
Note: Some events do not support priorities because their invocation is not caused by the interrupt processing.
Warnings: Processor Expert does not allow you to decrease an event code priority (with the exception of 'Interrupts enabled' value on some platforms).
This is because Processor Expert event routines are not generally reentrant so there is a risk that the interrupt would be able to interrupt itself during the processing. If there is such functionality requested, you have to do it manually (for example, by calling a appropriate processor component method setting a priority) and carefully check possible problems.