FREERTOS: Free Real Time Operating System (from https://freertos.org/a00110.html) If configUSE_NEWLIB_REENTRANT is set to 1 then a newlib reent structure will be allocated for each created task. Note Newlib support has been included by popular demand, but is not used by the FreeRTOS maintainers themselves. FreeRTOS is not responsible for resulting newlib operation. User must be familiar with newlib and must provide system-wide implementations of the necessary stubs. Be warned that (at the time of writing) the current newlib design implements a system-wide malloc() that must be provided with locks. Warning: if enabled without using newlib, CubeMx project compilation will fail ("cannot open source file "reent.h") If Enabled (default value), copies the heap file (defined in "Memory Management scheme") from the FW pack to the generated project. If Disabled, it is up to the user to provide a file with, at least, vPortFree() and pvPortMalloc() implementations inside (they will otherwise be missing at linking time). Copies the heap file (defined in "Memory Management scheme") from the FW pack to the generated project. Can only be disabled on F4/F7/G0/G4/H7/L4/MP1/WB series (as a first step). TZEN=1 with non-secure context TZEN=0 TZEN=1 with non-secure context TZEN=0 Not in use. TZEN=1 with non-secure context TZEN=0 Not in use. Shows which API is used: CMSIS v1, CMSIS v2 or Native. Shows which API is used: CMSIS v1, CMSIS v2 or Native. Shows which API is used: CMSIS v1, CMSIS v2 or Native. Set to 1 to use the preemptive RTOS scheduler, or 0 to use the cooperative RTOS scheduler. This must be set to the frequency of the clock that drives the peripheral used to generate the kernels periodic tick interrupt. This is very often, but not always, equal to the main system clock frequency. This must be set to the frequency of the clock that drives the peripheral used to generate the kernels periodic tick interrupt. This is very often, but not always, equal to the main system clock frequency. Sets the tick interrupt frequency. The value is specified in Hz. Warning: The max value is 1000, as higher values generate compilation errors (division by zero) Sets the maximum priority that can be assigned to a task. Tasks can be assigned a priority from zero, which is the lowest priority, to (MAX_PRIORITIES-1), which is the highest priority. Warning: Set to 56 when CMSIS-RTOS v2 is in use. Sets the maximum priority that can be assigned to a task. Tasks can be assigned a priority from zero, which is the lowest priority, to (MAX_PRIORITIES-1), which is the highest priority. Sets the maximum priority that can be assigned to a task. Tasks can be assigned a priority from zero, which is the lowest priority, to (MAX_PRIORITIES-1), which is the highest priority. Sets the size of the stack allocated to the idle task. The value is specified in words (here, of 32 bits), not bytes. Warning: The value chosen by the user should take into account the number of threads, the total heap size and the system stack size. If the totality of used stack size is higher than the total heap size, FreeRTOS will not be able to create and manage the tasks. For information: max value = configTOTAL_HEAP_SIZE/4 (when allocation is dynamic) max value = MCU ram size/4 (when allocation is static) Sets the size of the stack allocated to the idle task. The value is specified in words (here, of 32 bits), not bytes. Warning: The value chosen by the user should take into account the number of threads, the total heap size and the system stack size. If the totality of used stack size is higher than the total heap size, FreeRTOS will not be able to create and manage the tasks. For information: max value = configTOTAL_HEAP_SIZE/4 (when allocation is dynamic) max value = MCU ram size/4 (when allocation is static) Sets the size of the stack allocated to the idle task. The value is specified in words (here, of 32 bits), not bytes. Warning: The value chosen by the user should take into account the number of threads, the total heap size and the system stack size. If the totality of used stack size is higher than the total heap size, FreeRTOS will not be able to create and manage the tasks. For information: max value = configTOTAL_HEAP_SIZE/4 (when allocation is dynamic) max value = MCU ram size/4 (when allocation is static) Sets the maximum number of characters that can be used for the name of a task. The NULL terminator is included in the count of characters. The tick count is held in a variable of type portTickType. When USE_16_BIT_TICKS is set to 1 (Enabled), portTickType is defined to be an unsigned 16-bit type. When USE_16_BIT_TICKS is set to 0 (Disabled), portTickType is defined to be an unsigned 32-bit type. Using a 16-bit type can greatly improve efficiency on 8-bit and 16-bit microcontrollers, but at the cost of limiting the maximum block time that can be specified. Warning: Forced to 0 (Disabled) as the STM32 architecture is a 32 bit one. IDLE_SHOULD_YIELD controls the behavior of the idle task if there are application tasks that also run at the idle priority. It only has an effect if the preemptive scheduler is being used. - if IDLE_SHOULD_YIELD is set to 0, then the idle task will never yield to another task, and will only leave the Running state when it is preempted. - if IDLE_SHOULD_YIELD is set to 1, then the idle task will never perform more than one iteration of its defined functionality without yielding to another task if there is another idle priority task that is in the Ready state. This ensures a minimum amount of time is spent in the idle task when application tasks are available to run. Set to 1 to include mutex functionality in the build, or 0 to omit mutex functionality from the build. Forced to 1 when CMSIS_RTOS_V2 is used (constraint due to current cmsis_os2.c file in FW packs). Set to 1 to include recursive mutex functionality in the build, or 0 to omit recursive mutex functionality from the build. Forced to 1 when CMSIS_RTOS_V2 is used (constraint due to current cmsis_os2.c file in FW packs). Set to 1 to include recursive mutex functionality in the build, or 0 to omit recursive mutex functionality from the build. Forced to 0 (Disabled) when configUSE_MUTEXES equals to 0 (Disabled). Set to 1 to include counting semaphore functionality in the build, or 0 to omit counting semaphore functionality from the build. Forced to 1 when CMSIS_RTOS_V2 is used (constraint due to current cmsis_os2.c file in FW packs). Set to 1 to include counting semaphore functionality in the build, or 0 to omit counting semaphore functionality from the build. The queue registry has two purposes, both of which are associated with RTOS kernel aware debugging: 1.It allows a textual name to be associated with a queue for easy queue identification within a debugging GUI. 2.It contains the information required by a debugger to locate each registered queue and semaphore. The queue registry has no purpose unless you are using a RTOS kernel aware debugger. USE_APPLICATION_TASK_TAG must be defined as 1 for the vTaskSetApplicationTaskTag function to be available. This function is intended for advanced users only. A 'tag' value can be assigned to each task. This value is for the use of the application only - the RTOS kernel itself does not make use of it in any way. The FreeRTOS trace macros documentation page provides a good example of how an application might make use of this feature. Useless, hidden, memory allocation = static The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The total amount of RAM available to the RTOS kernel. TOTAL_HEAP_SIZE setting has no effect unless heap_1.c, heap_2.c, heap_4.c or heap_5.c are being used by the application (see Memory Management scheme parameter for more information). Warning: The value chosen by the user should take into account the application consumption of RAM otherwise it will lead to link issues! For information: min value = configMINIMAL_STACK_SIZE*4 The RTOS kernel allocates RAM each time a task, queue, mutex, software timer or semaphore is created. To replace and improve the use of C standard libray malloc() and free() functions, the FreeRTOS download includes four sample memory allocation implementations. The schemes are implemented in the heap_1.c, heap_2.c, heap_3.c, heap_4.c and heap5.c sources files respectively. The schemes defined by heap_1.c, heap_2.c, heap_4.c and heap_5.c allocate memory from a statically allocated array, known as the FreeRTOS heap. TOTAL_HEAP_SIZE sets the size of this array. The size is specified in bytes. The RTOS kernel allocates RAM each time a task, queue, mutex, software timer or semaphore is created. To replace and improve the use of C standard libray malloc() and free() functions, the FreeRTOS download includes four sample memory allocation implementations. The schemes are implemented in the heap_1.c, heap_2.c, heap_3.c, heap_4.c and heap5.c sources files respectively. The schemes defined by heap_1.c, heap_2.c, heap_4.c and heap_5.c allocate memory from a statically allocated array, known as the FreeRTOS heap. TOTAL_HEAP_SIZE sets the size of this array. The size is specified in bytes. Note: heap_user choice added for newlib support (will generate a heap_user.c file to be completed by the user). The RTOS kernel allocates RAM each time a task, queue, mutex, software timer or semaphore is created. To replace and improve the use of C standard libray malloc() and free() functions, the FreeRTOS download includes four sample memory allocation implementations. The schemes are implemented in the heap_1.c, heap_2.c, heap_3.c, heap_4.c and heap5.c sources files respectively. The schemes defined by heap_1.c, heap_2.c, heap_4.c and heap_5.c allocate memory from a statically allocated array, known as the FreeRTOS heap. TOTAL_HEAP_SIZE sets the size of this array. The size is specified in bytes. FreeRTOS can be configured to collect task run time statistics. The vTaskGetRunTimeStats() API function formats the collected run time statistics into a human readable table. GENERATE_RUN_TIME_STATS must be set to 1 (Enabled) for vTaskGetRunTimeStats() to be available. Note: when set to 1, two empty functions are generated in the freertos.c file (to be completed by the user) Set to 1 (Enabled) if you wish to include additional structure members and functions to assist with execution visualization and tracing. Forced to 1 (as configGENERATE_RUN_TIME_STATS==1, configUSE_STATS_FORMATTING_FUNCTIONS==1 and configSUPPORT_DYNAMIC_ALLOCATION==1), as required by tasks.c Set to 1 (Enabled) if you wish to include additional structure members and functions to assist with execution visualization and tracing. Set to 1 (Enabled) if you wish to include additional structure members and functions to assist with execution visualization and tracing. Set USE_TRACE_FACILITY and USE_STATS_FORMATTING_FUNCTIONS to 1 (Enabled) to include the vTaskList() and vTaskGetRunTimeStats() functions in the build. Setting either to 0 (Disabled) will omit vTaskList() and vTaskGetRunTimeStates() from the build. The idle task hook function is a hook (or callback) function that, if defined and configured, will be called by the idle task on each iteration of its implementation. - if USE_IDLE_HOOK is set to 1 (Enabled) then the application must define an idle task hook function: void vApplicationIdleHook(void). - if USE_IDLE_HOOK is set to 0 (Disabled) then the idle task hook function will not be called, even if one is defined. Note: when set to 1, an empty function is generated in the freertos.c file (to be completed by the user) The tick hook function is a hook (or callback) function that, if defined and configured, will be called during each tick interrupt. - if USE_TICK_HOOK is set to 1 (Enabled) then the application must define a tick hook function: void vApplicationTickHook(void). - if USE_TICK_HOOK is set to 0 (Disabled) then the tick hook function will not be called, even if one is defined. Note: when set to 1, an empty function is generated in the freertos.c file (to be completed by the user) The malloc() failed hook function is a hook (or callback) function that, if defined and configured, will be called if pvPortMalloc() ever returns NULL. - NULL will be returned only if there is insufficient FreeRTOS heap memory remaining for the requested allocation to succeed. If USE_MALLOC_FAILED_HOOK is set to 1 (Enabled) then the application must define a malloc() failed hook function: void vApplicationMallocFailedHook(void). If USE_MALLOC_FAILED_HOOK is set to 0 (Disabled) then the malloc() failed hook function will not be called, even if one is defined. Note: when set to 1, an empty function is generated in the freertos.c file (to be completed by the user) FreeRTOS provides two optional mechanisms that can be used to assist in stack overflow detection and debugging. - when CHECK_FOR_STACK_OVERFLOW is set to 1 (option1), one mechanism is used - when CHECK_FOR_STACK_OVERFLOW is set to 2 (option2), both mechanisms are used. If CHECK_FOR_STACK_OVERFLOW is not set to 0 (Disabled), the application must provide a stack overflow hook (or callback) function: void vApplicationStackOverflowHook( xTaskHandle xTask, signed char *pcTaskName ); The kernel will call that stack overflow hook whenever a stack overflow is detected Note: when set to 1 or 2, a function with an empty body is generated in the freertos.c file (to be completed by the user) Set to 1 to include co-routine functionality in the build, or 0 to omit co-routine functionality from the build. To include co-routines croutine.c must be included in the project. Sets the maximum priority that can be assigned to a co-routine. Co-routines can be assigned a priority from zero, which is the lowest priority to (MAX_CO_ROUTINE_PRIORITIES-1), which is the highest priority. Set to 1 (Enabled) to include software timer functionality, or 0 (Disabled) to omit software timer functionality. Note: When enabled, memory will be allocated for the timer task: size requested (in Bytes) = 4 * configTIMER_TASK_STACK_DEPTH. Set to 1 (Enabled) to include software timer functionality. Dependency: Forced to 1 (Enabled) when - CMSIS_RTOS_V2 is used (constraint due to current cmsis_os2.c file in FW packs) - xTaskGetSchedulerState equals to 0 (Disabled) - xTimerPendFunctionCall equals to 1 (Enabled) - or xEventGroupSetBitFromISR equals to 1 (Enabled). Sets the priority of the software timer service/daemon task. Sets the priority of the software timer service/daemon task. Disabled as configUSE_TIMERS itself is disabled. Sets the size of the stack (in words, not bytes) allocated to the timer service task. Sets the size of the stack (in words, not bytes) allocated to the timer service task. Sets the size of the stack (in words, not bytes) allocated to the timer service task. Disabled as configUSE_TIMERS itself is disabled. Sets the length of the software timer command queue. Sets the length of the software timer command queue. Disabled as configUSE_TIMERS itself is disabled. The lowest interrupt priority that can be used in a call to a "set priority" function. The lowest interrupt priority that can be used in a call to a "set priority" function. The lowest interrupt priority that can be used in a call to a "set priority" function. The highest interrupt priority that can be used by any interrupt service routine that makes calls to interrupt safe FreeRTOS API functions. DO NOT CALL INTERRUPT SAFE FREERTOS API FUNCTIONS FROM ANY INTERRUPT THAT HAS A HIGHER PRIORITY THAN THIS! (higher priorities are lower numeric values). The highest interrupt priority that can be used by any interrupt service routine that makes calls to interrupt safe FreeRTOS API functions. DO NOT CALL INTERRUPT SAFE FREERTOS API FUNCTIONS FROM ANY INTERRUPT THAT HAS A HIGHER PRIORITY THAN THIS! (higher priorities are lower numeric values). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the vTaskPrioritySet() API function, set vTaskPrioritySet to 1 (Enabled) To exclude it from your build, set vTaskPrioritySet to 0 (Disabled) It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the uxTaskPriorityGet() API function, set uxTaskPriorityGet to 1 (Enabled). To exclude it from your build, set uxTaskPriorityGet to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the vTaskDelete() API function, set vTaskDelete to 1 (Enabled). To exclude it from your build, set vTaskDelete to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the vTaskCleanUpResources() API function, set vTaskCleanUpResources to 1 (Enabled). To exclude it from your build, set vTaskCleanUpResources to 0 (Disabled). Note: It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the vTaskSuspend() API function, set vTaskSuspend to 1 (Enabled). To exclude it from your build, set vTaskSuspend to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the vTaskSuspend() API function, set vTaskSuspend to 1 (Enabled). To exclude it from your build, set vTaskSuspend to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the vTaskDelayUntil() API function, set vTaskDelayUntil to 1 (Enabled). To exclude it from your build, set vTaskDelayUntil to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the vTaskDelayUntil() API function, set vTaskDelayUntil to 1 (Enabled). To exclude it from your build, set vTaskDelayUntil to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the vTaskDelay() API function, set vTaskDelay to 1 (Enabled). To exclude it from your build, set vTaskDelay to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the xTaskGetSchedulerState() API function, set xTaskGetSchedulerState to 1 (Enabled). To exclude it from your build, set xTaskGetSchedulerState to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the xTaskGetSchedulerState() API function, set xTaskGetSchedulerState to 1 (Enabled) To exclude it from your build, set xTaskGetSchedulerState to 0 (Disabled). Dependency: Forced to 1 (Enabled) as configUSE_TIMERS equals to 0 (constraint due to the call to xPortSysTickHandler() in the interruption file) Set to 1 to include the 'alternative' queue functions in the build, or 0 to omit the 'alternative' queue functions from the build. The alternative API is described within the queue.h header file. Note: The alternative API is deprecated and should not be used in new designs. Set to 1 to include the 'alternative' queue functions in the build, or 0 to omit the 'alternative' queue functions from the build. The alternative API is described within the queue.h header file. Note: The alternative API was deprecated some time ago, and was removed in FreeRTOS V9.0 0. It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the xTaskResumeFromISR() API function, set xTaskResumeFromISR and vTaskSuspend to 1 (Enabled). To exclude it from your build, set xTaskResumeFromISR or vTaskSuspend to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the xTaskResumeFromISR() API function, set xTaskResumeFromISR and vTaskSuspend to 1 (Enabled). To exclude it from your build, set xTaskResumeFromISR or vTaskSuspend to 0 (Disabled). Configuration constant introduced in FreeRTOS v7.2.0 that is used as the default value of xSemaphoreGetMutexHolder (if it is not explicitly set) Configuration constant introduced in FreeRTOS v7.2.0 that is used as the default value of xSemaphoreGetMutexHolder (if it is not explicitly set) It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the xSemaphoreGetMutexHolder() API function, set xSemaphoreGetMutexHolder and USE_MUTEXES to 1 (Enabled). To exclude it from your build, set xSemaphoreGetMutexHolder or USE_MUTEXES to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the pcTaskGetTaskName() API function, set pcTaskGetTaskName to 1 (Enabled). To exclude it from your build, set pcTaskGetTaskName to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the uxTaskGetStackHighWaterMark() API function, set uxTaskGetStackHighWaterMark to 1 (Enabled). To exclude it from your build, set uxTaskGetStackHighWaterMark to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the uxTaskGetStackHighWaterMark() API function, set uxTaskGetStackHighWaterMark to 1 (Enabled). To exclude it from your build, set uxTaskGetStackHighWaterMark to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the xTaskGetCurrentTaskHandle() API function, set xTaskGetCurrentTaskHandle to 1 (Enabled). To exclude it from your build, set xTaskGetCurrentTaskHandle to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the eTaskGetState() API function, set eTaskGetState to 1 (Enabled). To exclude it from your build, set eTaskGetState to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the eTaskGetState() API function, set eTaskGetState to 1 (Enabled). To exclude it from your build, set eTaskGetState to 0 (Disabled). Set bits (flags) within an RTOS event group. A version of xEventGroupSetBits() that can be called from an interrupt service routine (ISR). Note: INCLUDE_xTimerPendFunctionCall must be set to 1 to make the xEventGroupSetBitFromISR() function available. Set bits (flags) within an RTOS event group. A version of xEventGroupSetBits() that can be called from an interrupt service routine (ISR). Note: INCLUDE_xTimerPendFunctionCall must be set to 1 to make the xEventGroupSetBitFromISR() function available. Dependency: Must be set to 0 (Disabled) when xTimerPendFunctionCall = 0 (Disabled). Used to pend the execution of a function to the RTOS daemon task (the timer service task, hence this function is pre-fixed with 'Timer'). Note: configUSE_TIMERS must be set to 1 to make the xTimerPendFunctionCall() function available Used to pend the execution of a function to the RTOS daemon task (the timer service task, hence this function is pre-fixed with 'Timer'). Note: configUSE_TIMERS must be set to 1 to make the xTimerPendFunctionCall() function available Used to pend the execution of a function to the RTOS daemon task (the timer service task, hence this function is pre-fixed with 'Timer'). Note: configUSE_TIMERS must be set to 1 to make the xTimerPendFunctionCall() function available Dependency: Forced to 0 (Disabled) as configUSE_TIMERS is Disabled. The FreeRTOS.h header file includes a set of #define macros that map the names of data types used in versions of FreeRTOS prior to version 8.0.0 to the names used in FreeRTOS version 8.0.0. The macros allow application code to update the version of FreeRTOS they are built against from a pre 8.0.0 version to a post 8.0.0 version without modification. Setting configENABLE_BACKWARD_COMPATIBILITY to 0 in FreeRTOSConfig.h excludes the macros from the build, and in so doing allowing validation that no pre version 8.0.0 names are being used. Some FreeRTOS ports have two methods of selecting the next task to execute - a generic method, and a method that is specific to that port. The Generic method: - Is used when configUSE_PORT_OPTIMISED_TASK_SELECTION is set to 0, or when a port specific method is not implemented. - Can be used with all FreeRTOS ports. - Is completely written in C, making it less efficient than a port specific method. - Does not impose a limit on the maximum number of available priorities. A port specific method: - Is not available for all ports. - Is used when configUSE_PORT_OPTIMISED_TASK_SELECTION is set to 1. - Relies on one or more architecture specific assembly instructions (typically a Count Leading Zeros [CLZ] of equivalent instruction) so can only be used with the architecture for which it was specifically written. - Is more efficient than the generic method. - Typically imposes a limit of 32 on the maximum number of available priorities. Some FreeRTOS ports have two methods of selecting the next task to execute - a generic method, and a method that is specific to that port. The Generic method: - Is used when configUSE_PORT_OPTIMISED_TASK_SELECTION is set to 0, or when a port specific method is not implemented. - Can be used with all FreeRTOS ports. - Is completely written in C, making it less efficient than a port specific method. - Does not impose a limit on the maximum number of available priorities. A port specific method: - Is not available for all ports. - Is used when configUSE_PORT_OPTIMISED_TASK_SELECTION is set to 1. - Relies on one or more architecture specific assembly instructions (typically a Count Leading Zeros [CLZ] of equivalent instruction) so can only be used with the architecture for which it was specifically written. - Is more efficient than the generic method. - Typically imposes a limit of 32 on the maximum number of available priorities. Warning: Forced to 1 (Enabled) since FreeRTOS v9 support. By setting the configUSE_TICKLESS_IDLE, the idle task suppresses ticks and the processor stays in a low power mode for as long as possible. - when set to 1 (Built in functionality enabled), two macros, configPRE_SLEEP_PROCESSING and configPOST_SLEEP_PROCESSING are generated in FreeRTOSConfig.h, and two empty functions, PreSleepProcessing and PostSleepProcessing generated in freertos.c (to be completed with user code). - when set to 2 (User defined functionality enabled), TO COMPLETE... By setting the configUSE_TICKLESS_IDLE, the idle task suppresses ticks and the processor stays in a low power mode for as long as possible. By setting the configUSE_TICKLESS_IDLE, the idle task suppresses ticks and the processor stays in a low power mode for as long as possible. Each RTOS task has a 32-bit notification value. An RTOS task notification is an event sent directly to a task that can unblock the receiving task, and optionally update the receiving task's notification value. RTOS task notification functionality is enabled by default, and can be excluded from a build (saving 8 bytes per task) by setting configUSE_TASK_NOTIFICATIONS to 0 in FreeRTOSConfig.h (achieved when setting USE_TASK_NOTIFICATIONS to Disabled). Must be set to 1 if the application writer wants to provide their own implementation of vPortSetupTimerInterrupt(). Must be set to 1 if the application writer wants to provide their own implementation of vPortSetupTimerInterrupt(). FreeRTOS versions prior to V9.0.0 allocate the memory used by the RTOS objects listed below from the special FreeRTOS heap. FreeRTOS V9.0.0 and onwards gives the application writer the ability to instead provide the memory themselves, allowing the following objects to optionally be created without any memory being allocated dynamically: Tasks, Software Timers, Queues, Event Groups, Semaphores and Mutexes. For that purpose, two new parameters are available: configSUPPORT_DYNAMIC_ALLOCATION and configSUPPORT_STATIC_ALLOCATION. (see http://www.freertos.org/Static_Vs_Dynamic_Memory_Allocation.html for more information). In CubeMx, setting MEMORY_ALLOCATION allows to configure configSUPPORT_STATIC_ALLOCATION and configSUPPORT_DYNAMIC_ALLOCATION parameters at the same time: - when equals to "Dynamic", sets configSUPPORT_DYNAMIC_ALLOCATION to 1 and configSUPPORT_STATIC_ALLOCATION to 0 - when equals to "Static", sets configSUPPORT_DYNAMIC_ALLOCATION to 0 and configSUPPORT_STATIC_ALLOCATION to 1 - when equals to "Dynamic / Static", sets both configSUPPORT_DYNAMIC_ALLOCATION and configSUPPORT_STATIC_ALLOCATION to 1 Note: Forced to 2 (Dynamic / Static), constraint due to the current CMSIS-RTOS V2 files (mainly cmsis_os2.c). FreeRTOS versions prior to V9.0.0 allocate the memory used by the RTOS objects listed below from the special FreeRTOS heap. FreeRTOS V9.0.0 and onwards gives the application writer the ability to instead provide the memory themselves, allowing the following objects to optionally be created without any memory being allocated dynamically: Tasks, Software Timers, Queues, Event Groups, Semaphores and Mutexes. For that purpose, two new parameters are available: configSUPPORT_DYNAMIC_ALLOCATION and configSUPPORT_STATIC_ALLOCATION. (see http://www.freertos.org/Static_Vs_Dynamic_Memory_Allocation.html for more information). In CubeMx, setting MEMORY_ALLOCATION allows to configure configSUPPORT_STATIC_ALLOCATION and configSUPPORT_DYNAMIC_ALLOCATION parameters at the same time: - when equals to "Dynamic", sets configSUPPORT_DYNAMIC_ALLOCATION to 1 and configSUPPORT_STATIC_ALLOCATION to 0 - when equals to "Static", sets configSUPPORT_DYNAMIC_ALLOCATION to 0 and configSUPPORT_STATIC_ALLOCATION to 1 - when equals to "Dynamic / Static", sets both configSUPPORT_DYNAMIC_ALLOCATION and configSUPPORT_STATIC_ALLOCATION to 1 FreeRTOS versions prior to V9.0.0 allocate the memory used by the RTOS objects listed below from the special FreeRTOS heap. FreeRTOS V9.0.0 and onwards gives the application writer the ability to instead provide the memory themselves, allowing the following objects to optionally be created without any memory being allocated dynamically: Tasks, Software Timers, Queues, Event Groups, Semaphores and Mutexes. For that purpose, two new parameters are available: configSUPPORT_DYNAMIC_ALLOCATION and configSUPPORT_STATIC_ALLOCATION. (see http://www.freertos.org/Static_Vs_Dynamic_Memory_Allocation.html for more information). In CubeMx, setting MEMORY_ALLOCATION allows to configure configSUPPORT_STATIC_ALLOCATION and configSUPPORT_DYNAMIC_ALLOCATION parameters at the same time: - when equals to "Dynamic", sets configSUPPORT_DYNAMIC_ALLOCATION to 1 and configSUPPORT_STATIC_ALLOCATION to 0 - when equals to "Static", sets configSUPPORT_DYNAMIC_ALLOCATION to 0 and configSUPPORT_STATIC_ALLOCATION to 1 - when equals to "Dynamic / Static", sets both configSUPPORT_DYNAMIC_ALLOCATION and configSUPPORT_STATIC_ALLOCATION to 1 If USE_TIMERS and USE_DAEMON_TASK_STARTUP_HOOK are both set to 1 (Enabled) then the application must define an hook function: void vApplicationDaemonTaskStartupHook(void). Note: when set to 1, an empty function is generated in the freertos.c file (to be completed by the user) If USE_TIMERS and USE_DAEMON_TASK_STARTUP_HOOK are both set to 1 (Enabled) then the application must define an hook function: void vApplicationDaemonTaskStartupHook(void). Note: when set to 1, an empty function is generated in the freertos.c file (to be completed by the user). Dependency: Forced to 0 (Disabled) as USE_TIMERS equals to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the xTaskAbortDelay() API function, set xTaskAbortDelay to 1 (Enabled). To exclude it from your build, set xTaskAbortDelay to 0 (Disabled). It is one of the macros allowing those components of the real time kernel not utilized by your application to be excluded from your build. - this ensures the RTOS does not use any more ROM or RAM than necessary for your particular embedded application. To include the xTaskGetHandle() API function, set xTaskGetHandle to 1 (Enabled). To exclude it from your build, set xTaskGetHandle to 0 (Disabled). When set to 1 (Enabled) the stack start address is saved into each task's TCB (assuming stack grows down). Use or not Memory Protection Unit with FreeRTOS. Very first step of implementation on WB for Examples Migration. To be consolidated on F4. Use of Memory Protection Unit with FreeRTOS (not yet available, as requires support of FreeRTOS Native API). Use of Memory Protection Unit with FreeRTOS (not yet available, as requires support of FreeRTOS Native API). Use or not FPU with FreeRTOS. Use or not FPU with FreeRTOS. Defaults to size_t for backward compatibility, but can be overridden in FreeRTOSConfig.h if lengths will always be less than the number of bytes in a size_t. Not available in previous versions. Description to be completed. Not available in previous versions. Description to be completed. Not available in previous versions. Forced to 0 as Secure Context not possible. Forced to 1 when TZEN=1 Forced to 0 as TZEN=0. A new parameter coming with 10.2.1 on L5 used when TZEN=1. Fixed to 512 (need to know more about it). TBC A new parameter coming with 10.2.1 on L5. Not available for others yet. FREERTOS_ENABLE_Init FREERTOS_CMSIS_V2_ENABLE_Init FREERTOS_NATIVE_ENABLE_Init S_FREERTOS$context S_CMSIS_RTOS_V1$context S_FREERTOS_ACTIVATED