Advanced: Creating Customized OSIs : Customizing API Definitions : Customizing the Static OS Configuration : Where Definition is Used, Code Generated

Where Definition is Used, Code Generated

For OSIs that use a static OS configuration file, you provide the names of the following two files, when defining the profile to use for code generation:

The template file to use for the creation of the OS configuration file.

The keywords used in the template file will be replaced with concrete data from the model to create the OS configuration file that reflects the OS objects in the model.

OS CFG Output

The name to use for the generated static OS configuration file.

The task, event, timer, synchronization, critical section, message, and ISR definitions listed in the tables in this section are used for building the file used for generation of the static OS configuration file.

The following code will be generated for an activity named T1, defined to be a task:, and the input file given below.

Input File:


task_definition_keyword_1

task_definition_keyword_6
semaphore_definition_keyword_9

event_definition_keyword_4
...

Generated Code:


task_definition_1

task_definition_6
semaphore_definition_9

event_definition_4
...