we are using a K66FX1M0VMD18 processor with KDS 3.0, KSDK 1.2.0, ProcessorExpert and MQX.
From time to time, I observed that my software got stuck and the debugger stopped in dispatch.S at /* woohoo, idle task must be enabled, this point cannot be reachable, you have serious problem */. I found out that because of an an unhandled interrupt, the default ISR from MQX _int_default_isr() got called. The problem is, that this routine suspends the current task!! So if the current task coincidently is the idle task when the unhandled interrupt occurs, the idle task is blocked and there is no task left to run!
Is this a bug in MQX or how is _int_default_isr() meant to work? In my opinion, the idle task should never be blocked, even if unhandled interrupts or exceptions occur.