Greetings,
When will the current CCS5.x support Animate run mode, especially for a n MC device.
Sam
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Greetings,
When will the current CCS5.x support Animate run mode, especially for a n MC device.
Sam
Sam,
The “animate” terminology is no longer used in CCSv4 and v5, but the equivalent functionality is available through the breakpoint view. Have a look at the available breakpoint actions in the breakpoint properties view and select “refresh all windows”, for example.
Regards,
Bhavin
Greetings,
Is your hint here that the CPU will hit a BP, update views and resume running?
Also, I would like the debugger to permit me to place a BP on the fly, without having to halt the CPU, like what CCS3.x had.
Regards,
Sam
Sam,
Yes, What was called “Animate” in v3.x would run to a breakpoint, update all views, and run again. In v4 or v5, if you set a breakpoint with an action of “update all views”, you get the same behavior.
C6x should not have any issues setting BP or accessing memory while target is running. ICEMaker on DSP supports that.
Regards,
Bhavin
Greetings,
I got it to do what I wanted on a single CPU (using 6678 EVM) using "update all views", but It sometime redlines on many CPUs.
I am using CCS5.1.1.00031.
Re. the BP Q, I do get the following sometime
Hi,
When does this error messages come? Is it when you try to do something (Please let me know what is that) OR during normal running after enabling "update all views"?
Regards,
Bhavin
I get this random when I attempt to enable or disable a BP while CPUs are running.
CCSv5 requires you to halt to set a breakpoint. This message should not be random but should occur every time you try to set a breakpoint while running. Earlier versions of CCS would appear to set the breakpoint while running but actually halted the target, set the breakpoint and then run it again. Most users didn't realize that this is what was happening. Thus the default behavior has changed in CCSv5.
Regards,
John