This issue is just a very small inconvenience problem, but I'd like to ask anyway.
When I debug a 3-core project on ADZS-SC589-EZLITE development board, such as the "ThreeCore_SC589" example included in the dev board support package, CCES first loads executable code in memory then hits the automatic/default breakpoint in first statement of main() in the Core 0 project. The focus in the Debug window is automatically on that breakpoint so that I can simply press the F5 key or click the resume button on the toolbar to start Core 0 running:
After I press the F5 key, Core 0 starts running and the automatic/default breakpoint for Core 1 main() function is hit. The focus in the Debug window automatically shifts to this breakpoint and I can can simply press the F5 key or click the resume button on the toolbar to start Core 1 running:
After I press the F5 key, Core 1 starts running, however the focus in the Debug window does not automatically shift to the Core 2 breakpoint, Core 1 remains highlighted:
Now I am unable to simply press F5 key to start Core 2 running - I must use the mouse to click on Core 2 in the Debug window (highlight Core 2) and then I can use F5 or the Resume button to start Core 2 running.
My question: Why doesn't CCES automatically shift its breakpoint focus to Core 2 after I start Core 1? Is there some setting adjustment which will change CCES behavior to automatically shift focus to Core 2 in the situation described above?
I know this is a very small issue - but sitting at a lab bench all day starting many many debug sessions, it starts to become annoying.
Thanks in advance for your help!
Your suggestion works great - thanks very much!