AnsweredAssumed Answered

VLLS2 Deep Sleep Causes KDE to Halt CPU

Question asked by Leif Zars on Mar 11, 2015
Latest reply on Mar 26, 2017 by Kerry Zhou

When in a debugging session and when the k20 goes to VLLS2 deep sleep KDS acts oddly. Works as expected in CW.

Going in to VLLS2 the debugger pauses, and shows a stack trace of:

__Vec_Table() at 0x0



the arm-non-eabi-gdb console shows:

Program received signal SIGTRAP, Trace/breakpoint trap.

0x00000000 in __vect_table ()


When I try to resume executions nothing works. This worked fine in CodeWarrior.

When I run the code with the debugger detached it goes to sleep and wakes up as expects.