![]() The scheduler is suspended, or calling an API function that doesĤ) Using a queue or semaphore before it has been initialised orīefore the scheduler has been started (are interrupts firingīefore vTaskStartScheduler() has been called?). Seeģ) Calling an API function from within a critical section or when Interrupt priories, which can seem counter intuitive. Parts where numerically high priority values denote low actual ![]() If you find your application is crashing here then likely causes are:Ģ) Incorrect interrupt priority assignment, especially on Cortex-M3 (I have increased the Stack but without success) Now i have defined the configASSERT but it doesn’t trap into the vAssertCalled function.Īctually, the code stops at this position:
0 Comments
Leave a Reply. |