vTaskSwitchContext() usage of listGET_...

em1ssnuke wrote on Wednesday, October 22, 2008:

vPreemptiveTick() calls vTaskSwitchContext() usage of listGET_OWNER_OF_NEXT_ENTRY() causes __dabt().  Unfortunately there is no task at this point to execute. 

This appears to be a race condition of letting the tick counter generate ticks while tasks are just getting initialized.  I assume the tick generation should not occur until after the tasks have been initialized and prior to vTaskStartScheduler().   Now locating where the tick generation has been initiated.

davedoors wrote on Wednesday, October 22, 2008:

You have not mentioned which port you are using. If using Cortex M3 then this can happen if you attempt to block from within a critical section. It can also happen on any port if you have your interrupt priorities wrong, that is you are using API calls from an interrupt priority about the maximum allowable system call interrupt priority.

em1ssnuke wrote on Wednesday, October 22, 2008:

This is part of the same problem as https://sourceforge.net/forum/forum.php?thread_id=2412378&forum_id=382005.