Updated Jun 2025
xTaskCreate
task.h
1 BaseType_t xTaskCreate( TaskFunction_t pvTaskCode,2 const char * const pcName,3 const configSTACK_DEPTH_TYPE uxStackDepth,4 void *pvParameters,5 UBaseType_t uxPriority,6 TaskHandle_t *pxCreatedTask7 );
Create a new task and add it to the list of tasks that are ready to run. configSUPPORT_DYNAMIC_ALLOCATION must be set to 1 in FreeRTOSConfig.h, or left undefined (in which case it will default to 1), for this RTOS API function to be available.
Each task requires RAM that is used to hold the task state, and used by the task as its stack. If a task is created using xTaskCreate() then the required RAM is automatically allocated from the FreeRTOS heap. If a task is created using xTaskCreateStatic() then the RAM is provided by the application writer, so it can be statically allocated at compile time. See the Static Vs Dynamic allocation page for more information.
If you are using FreeRTOS-MPU then we recommend that you use xTaskCreateRestricted() instead of xTaskCreate().
Parameters:
-
pvTaskCode
Pointer to the task entry function (just the name of the function that implements the task, see the example below). Tasks are normally implemented as an infinite loop; the function which implements the task must never attempt to return or exit. Tasks can, however, delete themselves.
-
pcName
A descriptive name for the task. This is mainly used to facilitate debugging, but can also be used to obtain a task handle. The maximum length of a task's name is defined by configMAX_TASK_NAME_LEN in FreeRTOSConfig.h.
-
uxStackDepth
The number of words (not bytes!) to allocate for use as the task's stack. For example, if the stack is 16-bits wide and uxStackDepth is 100, then 200 bytes will be allocated for use as the task's stack. As another example, if the stack is 32-bits wide and uxStackDepth is 400 then 1600 bytes will be allocated for use as the task's stack. The stack depth multiplied by the stack width must not exceed the maximum value that can be contained in a variable of type size_t. See the FAQ How big should the stack be?.
-
pvParameters
A value that is passed as the paramater to the created task. If pvParameters is set to the address of a variable then the variable must still exist when the created task executes - so it is not valid to pass the address of a stack variable.
-
uxPriority
The priority at which the created task will execute. Systems that include MPU support can optionally create a task in a privileged (system) mode by setting the bit portPRIVILEGE_BIT in uxPriority. For example, to create a privileged task at priority 2 set uxPriority to ( 2 | portPRIVILEGE_BIT ). Priorities are asserted to be less than configMAX_PRIORITIES. If configASSERT is undefined, priorities are silently capped at (configMAX_PRIORITIES - 1).
-
pxCreatedTask
Used to pass a handle to the created task out of the xTaskCreate() function. pxCreatedTask is optional and can be set to NULL.
Returns:
- If the task was created successfully then pdPASS is returned.
- Otherwise errCOULD_NOT_ALLOCATE_REQUIRED_MEMORY is returned.
Example usage:
1/* Task to be created. */2void vTaskCode( void * pvParameters )3{4 /* The parameter value is expected to be 1 as 1 is passed in the5 pvParameters value in the call to xTaskCreate() below. */67 configASSERT( ( ( uint32_t ) pvParameters ) == 1 );89 for( ;; )10 {11 /* Task code goes here. */12 }13}1415/* Function that creates a task. */16void vOtherFunction( void )17{18 BaseType_t xReturned;19 TaskHandle_t xHandle = NULL;2021 /* Create the task, storing the handle. */22 xReturned = xTaskCreate(23 vTaskCode, /* Function that implements the task. */24 "NAME", /* Text name for the task. */25 STACK_SIZE, /* Stack size in words, not bytes. */26 ( void * ) 1, /* Parameter passed into the task. */27 tskIDLE_PRIORITY,/* Priority at which the task is created. */28 &xHandle ); /* Used to pass out the created task's handle. */2930 if( xReturned == pdPASS )31 {32 /* The task was created. Use the task's handle to delete the task. */33 vTaskDelete( xHandle );34 }35}