Advanced: Creating Customized OSIs : Customizing API Definitions : General API Definitions : Scheduler Definition APIs

Scheduler Definition APIs

A scheduler file is a file that includes the Tasks defined in the application.

If this option is selected, the code generator will look for the specified scheduler file, and insert the list of Tasks to be performed.

File Name

By default, the tasks are added to the file <Profile Name>.c. If you want the generator to use a different file, enter the name of the file in the text box or use the ... button to select the file.

These are the words that demarcate the beginning and end of the task list. The code generator requires the end keyword as well because it removes the tasks that were previously included in the list.

The keywords used can include tokens enclosed with "$<" and ">" (API definition notation).

When using "$<token>" as part of the keyword, the name of the keyword can vary between groups of tasks, depending on the data of the task. The tokens that can be used are:

For example:

If a task has a design attribute named "CK_timeSlice" with three possible values ("10ms", "40ms" and "100ms"), and the begin and end keywords are defined as /* User $<CK_timeSlice> Tasks Begin */\, and /* User $<CK_timeSlice> Tasks End */respectively, then tasks with CK_timeSlice = 40ms will be put in the scheduler file between the keywords /* User 40msTasks Begin */\ and the keyword /* User 40ms Tasks End */

Task Separator

The delimiter to use to separate the individual tasks in the list. When using a custom delimiter, you can use "\n" to specify a new line.