14.なぜデバッグが二回目にうまくいかないのでしょうか？
14.なぜデバッグが二回目にうまくいかないのでしょうか？
Atollic TrueSTUDIO® has a very powerful windowing system, that allow developers to switch forwards and backwards across multiple window layouts (perspectives). By switching perspectives (i.e changing the window setup), developers will see a different set of windows and docking views, suitable for various purposes. But by changing perspective, background activities are not stopped, you only change what windows and views you currently see.In particular, this means that by switching from the Debugger perspective, into for example the C/C++ perspective, the existing debug session is not stopped. You only temporarily change the window setup, and can at any time switch back to the debug session by switching back to the Debug perspective.
Effectively, this means that leaving the Debug perspective does not stop the debugger, as the debug session continues in the background. So by leaving the Debug perspective without first stopping execution of the application being debugged, the debug system continue to debug using the (most likely) one and only JTAG probe connected.
If you in this situation go back to the C/C++ perspective, make some code changes and rebuild the application, and try to start debugging the changed application, this will fail, as the debugger is still busy debugging the older version of the application, using your one and only JTAG probe.
To be able to start a new debug session, the currently running debug session must first be stopped, using the "red square" toolbar icon in the "Debug" view or using the "Run, Terminate" menu command.
Good practice is to always terminate the debug session before leaving the Debug perspective if you intend to restart a different debug session soon. If you still end up in this situation, switch to the Debug perspective, terminate the old debug session, switch back to the C/C++ perspective and launch a new debug session.