Setting task priority before starting the scheduler

[aggarg (Gaurav Aggarwal)]

@crm7rt

The user can decide how many tasks he/she creates and some of them come from the framework, so that the total number is known at compile-time.

As others already suggested, you can consider several other approaches -

1. Place more restrictions on what priorities user tasks can have.
2. Place a restriction that no user task can have maximum priority (i.e. configMAX_PRIORITIES - 1) and then create one task with max priority in the framework which can be used for priority re-assignments. If you are using FreeRTOS timers, you can create the timer task at the highest priority and use configUSE_DAEMON_TASK_STARTUP_HOOK for priority re-assignments - Hook Functions - FreeRTOS™.

@crm7rt

I think the yield should be delayed since the priority configuration changed after a call to vTaskpriorityset and it does not make sense to trigger a task switch while the scheduler is suspended.

This is taken care in the vTaskSwitchContext.