Getting Started#

Any Connect application can be easily turned into an application running on an RTOS. To complete this task, install the RTOS component of your choice; for example, Micrium OS kernel or FreeRTOS. This will install all dependencies in the connect stack required to support RTOS operation.

The default setup should be good for most usecases, but if you need to fine-tune Connect’s RTOS implementation, some options are configurable in config/cmsis-rtos-ipc-config.h.

• EMBER_AF_PLUGIN_CMSIS_RTOS_CPU_USAGE: If 1, the Application Framework compiles in some additional code that allows certain debug tools to have extended debug information from the OS.

• EMBER_AF_PLUGIN_CMSIS_RTOS_CONNECT_STACK_PRIO: The priority of the task running the stack. Note that this is defined in CMSIS-RTOSv2 priority.

• EMBER_AF_PLUGIN_CMSIS_RTOS_CONNECT_STACK_SIZE: The size in bytes of the call stack used by the stack task.

• EMBER_AF_PLUGIN_CMSIS_RTOS_APP_FRAMEWORK_PRIO: The priority of the task running the application. Note that this is defined in CMSIS-RTOSv2 priority.

• EMBER_AF_PLUGIN_CMSIS_RTOS_APP_FRAMEWORK_STACK_SIZE: The size in bytes of the call stack used by the Application Framework task.

• EMBER_AF_PLUGIN_CMSIS_RTOS_MAX_CALLBACK_QUEUE_SIZE: Defines the maximum supported number of simultaneous callback messages from the stack task to the application tasks.

Installing any RTOS can change the behavior of other components as well. For example, the CLI Core component will also create an RTOS task for itself, while normally it is called from the main while loop.