rtel wrote on Tuesday, May 13, 2014:
Where do you end up when the exception occurs? If it is in a fault handler then you can get some information from the CAUSE register and try and work backwards from that to find the (actual) cause, but…
…if you only have two tasks, and the only function you are calling is vTaskDelayUntil(), and the only interrupt is the RTOS’s own tick interrupt, then there cannot be many things that could cause the problem.
Which heap_x.c implementation are you using, and what do you have configTOTAL_HEAP_SIZE set to? (http://www.freertos.org/a00111.html)
Did you base your application on one the official demo for that part, or did you create it from scratch yourself? If you used the official demo as a start, but the part number you are using is not the same as used in the official demo, did you ensure the project was targeted to the new chip (things like the linker script is correctly describing the memory on the device, etc.).
What do you have configMINIMAL_STACK_SIZE and configIRQ_STACK_SIZE set to in FreeRTOSConfig.h?