I have resolved my auto-start problem and I am now successfully executing code in “debug” and “run” mode, and in standalone mode with the debug link physically disconnected.
Previously, I experienced the same auto-start problem on three different hardware platforms. One Kinetis K20 and two custom hardware platforms. I also experienced the same problem using Code Warrior 10.2 and 10.5, regardless of whether I was using the OSJTAG or PnE MultiLink debug link. I am still working through the steps I took to correct the multiple problems I was having, but it appears that the primary cause of my auto-start problem may have been the fact that I had a “printf” in my code. I will double check next week, but it appears that the support for the “printf”, which allows the developer to write text to the console window, does not ignore the fact that the debug link is disconnected, logically or physically. As a result, the code stops executing. If this is true, there must be a way to resolve this in the CodeWarrior / Processor Expert development environment without explicitly removing the “printf” commands from the code. As you know, not all projects have a serial output port enabled and the use of “printf” commands to present messages to the console window when connected to the target is an extremely valuable tool.
