AN3423

Optimization

Doc ID 018987 Rev 2

9/13

The Startup and Shutdown Hooks belonging to applications are called directly without

saving context. This means that they run as trusted code and cannot be killed.

●

OS_EXCLUDE_KILLABLE_ISR

Interrupt service routines are called directly without saving context. This means that they run

as trusted code and cannot be killed.

●

OS_EXCLUDE_KILLALARM

The function for killing an alarm is omitted. It means an application with an active alarm

cannot be properly terminated.

●

OS_EXCLUDE_KILLISR

The function for killing an ISR is omitted. It means an ISR can never be killed in response to

a protection error.

●

OS_EXCLUDE_KILLTASK

The function for killing a task is omitted. It means a Task cannot be killed in response to a

protection error.

●

OS_EXCLUDE_MULTIPLE_ACTIVATIONS

If there are no tasks with multiple activations, quite a lot of code in ActivateTask and

TerminateTask can be omitted.

●

OS_EXCLUDE_PARAMETERACCESS

If the error hooks do not need to determine what API parameters cause the error, the code

that passes the parameters through the error handling can be omitted. It affects all API

functions.

●

OS_EXCLUDE_POSTISRHOOK

The code that calls the PostISRHook is omitted.

●

OS_EXCLUDE_POSTTASKHOOK

The code that calls the PostTaskHook is omitted.

●

OS_EXCLUDE_PREISRHOOK

The code that calls the PreISRHook is omitted.

●

OS_EXCLUDE_PREEMPTION

Architecture-dependent: the possible context switch at the end of the interrupt handler can

be simplified.

●

OS_EXCLUDE_PRETASKHOOK

The code in the error handler that calls the PreTaskHook is omitted.

●

OS_EXCLUDE_PROTECTION

All code related to memory protection is omitted.

●

OS_EXCLUDE_PROTECTIONHOOK

The code in the error handler that calls the ProtectionHook is omitted.

●

OS_EXCLUDE_RATEMONITORS

All the arrival rate limiting code in ActivateTask, SetEvent, WaitEvent and in the handling of

Category 2 ISRs is omitted.

●

OS_EXCLUDE_RESOURCEONISR