Hello botao yang,
Are you using breakpoints?? Which MQX version are you using???
The Debugger will consider BreakPoint as a trap or exception when debugging. Since user's task has higher priority than the system (MQX) idle task. When there is a breakpoint in user's task, the CPU (CPU core of target MCU) will stop the current task at the breakpoint place and then let the debugger to handle this breakpoint issue. As you know, MQX is a multi-task system, during the time period the debugger preparing the breakpoint issue, the CPU loaded the idle task to execute and then got the "stop" instruction from Debugger and then stop there.That is why Debugger stops at the entry point of idle task.If resume the application, the Debugger will then stops at the breakpoint which was set before.
Have a great day,
Sol
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------