AnsweredAssumed Answered

Unknown gdb command exec-run?

Question asked by Nathan Bazzell on Jun 20, 2019
Latest reply on Jul 4, 2019 by LPCX presso support

Debugging the hello world example from MCUXpresso IDE using a JLinkPro debugger gives the error "Failed to execute MI Command" "exec-run" "Don't know how to run." How can I fix this to enable debugging?


This is using the SDK_2.x_FRDM-K82F kit at Version 2.6.0 built for MCUXpressoIDE toolchain.


In the GDB trace log I can see it looks like the exec-run command was unknown.  I've included this and other logs in the attached file but the relevant contents are:


929,408 (gdb)
929,409 38-exec-run --thread-group i1
929,409 38^error,msg="Don't know how to run. Try \"help target\"."
929,410 (gdb)
929,414 39-gdb-exit
929,414 39^exit
929,414 =thread-group-exited,id="i1"


(UPDATE: The error is the same regardless if using a JLinkPro via USB, JLinkPro via Ethernet or onboard the OpenSDA debugger.)

(UPDATE: We see the same error with both Windows and Linux hosts using MCUXpresso IDE v11.0.0 build 2516.)


It seems to me the GDB commands MCUXpresso is trying to use are incompatible with the SDK but everything is at the latest so unsure why this would be or if I have some miss-configuration I'm aware of.  Any help would be appreciated!